Hi, On 2009/11/12, at 19:46, Cliff Spradlin wrote:
> Along the same lines.. I feel like instead of the custom header > compression being done here, you could do one of two things. Either > use short-form headers (the ones specified in the IMF like 'l' for > Content-Length'), or just compress the entire stream as a single gzip > instance. If the spec is going to send the data by default as gzip > anyway, might as well compress the headers as part of the same gzip > instance. Sure, a single gzip session makes a lot of sense. Unless you consider a proxy that bundles into the same SPDY stream several requests from different back-end servers. In that case, the proxy needs to uncompress from the back-end and compress to the client. With the current logic, each backend server can compress his own stuff, and the proxy just switches frames. On the other hand SSLv3 already includes compression, and if SSL is strongly recommended, you are doing double compression. best regards, -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
