2 ms·
I work for Google on Chromium (primarily networking stuff, like SPDY). You can see my comments on this matter here: https://groups.google.com/d/topic/spdy-dev/i
by afimrishi 14y ago
I work for Google on Chromium (primarily networking stuff, like SPDY). You can see my comments on this matter here: https://groups.google.com/d/topic/spdy-dev/ipTmn5ty_n0/discussion https://groups.google.com/d/topic/spdy-dev/ipTmn5ty_n0/discu....
"Our plan is to continue what we've been doing: experimenting with new ideas in SPDY and recommending the good ones for standardization in IETF (http://tools.ietf.org/html/draft-mbelshe-httpbis-spdy-00 http://tools.ietf.org/html/draft-mbelshe-httpbis-spdy-00). In the end, we only want one protocol, so we don't intend to keep a SPDY track alive longer than a successful standards process."
Out of curiosity, what changes from Speed + Mobility would you like to see in SPDY? We'd love to hear your recommendations on spdy-dev@googlegroups.com.
- 0xABADC0DA 14y agoWhat changes would I like to see? I'd like to see you work with Microsoft (and others) to improve the protocol. Microsoft with S+M has made real improvements. Ask them. They know their stuff. For me though, I think Microsoft held back on changes so it would be more accepted as Spdy-like. For instance the whole HTTP format seems pretty lame to me... a 16-bit string length count... amazing, iirc it's 32-bit now but who ever thought that was a good idea?!