Hi, I like some of the ideas behind SPDY, but I find its implementation to be too complex vs. its rewards.
Out-of-order pipelined responses can be done by extending the HTTP spec to include a 'request-id' or something along these lines. If you have a long-running stream of incoming, it's okay for that stream to be created using a new socket.. I think the SCTP-like protocol on top of TCP destroys the inherent debuggability of HTTP and the internet message format. 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. I think the use-case of switching tabs to be a reason to implement priority (and therefore SCTP-like streams on TCP) to be pretty weak.. people in multiple tabs generally are looking at different sites, and so changing the priority for the connection in the background tab isn't going to make any difference. Basically what I'm saying is.. please implement SPDY with only minimal modifications to HTTP. I think that with some minimal modifications you can get the majority of the performance increase you're looking for. P.S. I think the idea of being able to do an IP redirection without changing hostname is extremely cool. -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
