News for hackers. Stuff that matters.
Re:Introducing Shadow DOM API by nostrademons on Monday October 26, 2015 @04:19PM (#10454157)
HTTP2. In the HTTP2 world, extra requests don't add any additional latency. The browser multiplexes them over a single connection. I think I'd heard that it even uses a common compression dictionary for all requests, which means that boilerplate code that's duplicated between components will get compressed away.
Re:Introducing Shadow DOM API by lenish on Monday October 26, 2015 @06:10PM (#10454852)
>In the HTTP2 world, extra requests don't add any additional latency.

They don't add any additional TCP connection latency, sure. I think it's a bit unrealistic to claim there won't be any congestion of the multiplexed stream which causes additional latency.

>I think I'd heard that it even uses a common compression dictionary for all requests, which means that boilerplate code that's duplicated between components will get compressed away.

I may be misremembering, but I thought that was just for request headers?

Re:Introducing Shadow DOM API by alwillis on Tuesday October 27, 2015 @02:37AM (#10456613)
>I may be misremembering, but I thought that was just for request headers?

That's correct: https://http2.github.io/http2-spec/compression.html.

Re:Introducing Shadow DOM API by alwillis on Tuesday October 27, 2015 @02:44AM (#10456636)
HTTP2 also supports server push—the web server sends resources that the browser is going to need without waiting for them to be requested: http://blog.xebia.com/2015/08/23/http2-server-push/