4 ms·
I'd like to see an "enhanced" SPDY added to every browser and web server implementation, one that allows for a package of assets to be concatenated, compressed,
by mark242 15y ago
I'd like to see an "enhanced" SPDY added to every browser and web server implementation, one that allows for a package of assets to be concatenated, compressed, and sent in one chunk, rather than waiting for a browser to interpret HTML before starting to request more assets.
- pjscott 15y agoSPDY already supports server push, where a server can tell the client, "I'm sending over some files (e.g. JavaScript and CSS and a bunch of little images) that you're going to want soon. You're welcome." It sounds like exactly what you want.
- mark242 15y agoX-Associated-Content still requires each file to be broken out as its own, doesn't it? I'm thinking more of a single file with a manifest, highly compressed, that only requires one fopen() to push all of the data to the client. Sort of a browser cache warming file. "You need this Javascript, this CSS, and these images for any page on the site. Take this file and you're all set."
- pjscott 15y agoSince SPDY multiplexes multiple streams to the same socket, and commonly-used static content will be cached in the server's memory anyway, I don't see much practical difference between what SPDY's X-Associated-Content and what you're proposing.