3 ms·
All I really gathered from the presentation was that spriting and concatenation negate the caching advantages HTTP/2 could provide and are unnecessary. It doesn
by Silhouette 11y ago
All I really gathered from the presentation was that spriting and concatenation negate the caching advantages HTTP/2 could provide and are unnecessary. It doesn't make HTTP/2 worse than HTTP/1.1.
But changing an existing production site so it no longer uses techniques like spriting and concatenation will damage performance if anything degrades the communications to HTTP/1.1.
One point of standardizing HTTP/2 was to let the more conservative among us start to use it now.
I'm not sure anyone who is switching to HTTP/2 today could reasonably be called "conservative". There are few production-level servers available yet, and some of the big potential performance wins due to the multiplexing, prioritisation and server push aspects -- the things that in theory could render those spriting and concatenation techniques obsolete -- are barely even mentioned right now outside of the standards documentation and related announcements. I just spent a few minutes searching to see how you'd actually configure a web server to implement customised server push for maximum performance, and I literally didn't find a single explanation, nor for that matter a single server even advertising the capability.