News for hackers. Stuff that matters.

A comment on Https hurts users far away from the server. Parent comment

Re:Https hurts users far away from the server by jacquesm on Friday March 10, 2017 @11:55AM (#13839960)
> And infact reducing the number of requests using things like spritemaps, bundling js and css is actually an antipattern with http2.

Those are just ways to lose some of the impact of bloat without addressing the bloat itself.

If you address bloat directly it will benefit all users.

[ Parent | on HN ]
Re:Https hurts users far away from the server by dalore on Friday March 17, 2017 @10:08AM (#13894063)
If you shard on http2 it will take longer since now it makes multiple ssl connections which have have the ssl handshake.

With http2 it's all multiplexed into one connection. So you have the one ssl connection, but that one connection has multiplexed connections inside it. And since it's one tcp, the tcp sliding window has opened up and is actually faster then opening a new tcp connection.

[ Parent | on HN ]
Re:Https hurts users far away from the server by tuxracer on Friday March 10, 2017 @12:22PM (#13840207)
If you migrate to HTTP2 or move to a host that already supports it then cutting down on "round trips" is an obsolete concern altogether.
[ Parent | on HN ]
Re:Https hurts users far away from the server by jacquesm on Friday March 10, 2017 @01:15PM (#13840702)
HTTP2 does not magically bundle all connections to one. It still very much depends on how you build up your page.
[ Parent | on HN ]
Re:Https hurts users far away from the server by floatboth on Friday March 10, 2017 @02:45PM (#13841468)
It does not magically split one connections into many. One domain == one connection. Sure it won't undo your "domain sharding" hacks and merge your CDNs, yeah :)
[ Parent | on HN ]