3 ms·
This seems to bode badly for CDNs versus own tuned servers, unless there's a way for origin websites to provide hints on response ordering?
by mkj 10y ago
This seems to bode badly for CDNs versus own tuned servers, unless there's a way for origin websites to provide hints on response ordering?
- xzyfer 10y agoThere are discussions happening on how browsers can allow authors to resource prioritisation hints. I'm curious to see where it goes. We'd ideally like to be able to say – "prioritise 10 images in the viewport". You hack it together relatively efficiently using IntersectionObserver now, but support isn't great.
- toast0 10y agoCDNs are still going to have lower latency and higher bandwidth, and likely more ability to have long lived connections. Probably whatever mechanism develops to facilitate http/2 server pushed resources through a CDN will also include prioritization hints.
- hendry 10y agodamn, CloudFront already doesn't expose many tunables, so yeah, this isn't going to work. Starting to wish Appcache manifest actually was made to work and that could use used as a queue somehow to prioritise important assets on a Webpage.
- taf2 10y agoServiceWorkers are the app cache done right. https://github.com/w3c-webmob/ServiceWorkersDemos https://github.com/w3c-webmob/ServiceWorkersDemos
- hendry 10y agoMy point is that you can't map Service Workers onto a simple manifest, i.e. a list of resources the httpd needs to push as a priority. You "kindof" can with a Appcache "manifest". Stretch of the imagination, I know.