News for hackers. Stuff that matters.

A comment on Show HN: Initial release of H2O, and why HTTPD performance will matter in 2015. Parent comment

Re:Show HN: Initial release of H2O, and why HTTPD performanc... by zub on Thursday December 25, 2014 @06:10PM (#8797459)
> I can't see a way that new protocols are going to solve this, unless I'm missing something in how HTTP2 is going to be handled by the browser?

HTTP/2 server push. Your server can proactively deliver things like rollover state graphics knowing that the client will need them.

[ Parent | on HN ]
Re:Show HN: Initial release of H2O, and why HTTPD performanc... by robbles on Thursday December 25, 2014 @06:21PM (#8797490)
good point. I imagine determining when to push these assets will become a complex choice though.

Also, I realized shortly after commenting that I missed the obvious benefit of avoiding downloading global spritesheets and other compiled assets for individual pages that only use a subset of the content.

[ Parent | on HN ]