Re:Real-world HTTP/2: 400GB of images per day
by mkj on Thursday July 14, 2016 @09:39PM
(#12098462)
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?
[ Parent
| on HN ]
Re:Real-world HTTP/2: 400GB of images per day
by xzyfer on Thursday July 14, 2016 @09:43PM
(#12098474)
There 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.
Re:Real-world HTTP/2: 400GB of images per day
by toast0 on Thursday July 14, 2016 @10:11PM
(#12098567)
CDNs 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.
Re:Real-world HTTP/2: 400GB of images per day
by hendry on Thursday July 14, 2016 @10:31PM
(#12098623)
damn, 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.
Re:Real-world HTTP/2: 400GB of images per day
by taf2 on Thursday July 14, 2016 @11:26PM
(#12098780)
ServiceWorkers are the app cache done right. https://github.com/w3c-webmob/ServiceWorkersDemos
Re:Real-world HTTP/2: 400GB of images per day
by hendry on Thursday July 14, 2016 @11:29PM
(#12098789)
My 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.