The team behind nginx plan to roll out SPDY support at the end of May [1]. Will align nice with Firefox's support for SPDY!<p>[1] <a href="https://twitter.com/#!/nginxorg/status/192301063934705665" rel="nofollow">https://twitter.com/#!/nginxorg/status/192301063934705665</a>
Microsoft has submitted a proposal that is interesting for a few reasons. The requirement for encryption is optional and also the API/framing is closer to Websockets.<p><a href="http://tools.ietf.org/html/draft-montenegro-httpbis-speed-mobility-01" rel="nofollow">http://tools.ietf.org/html/draft-montenegro-httpbis-speed-mo...</a><p>If encryption is required, I can see many complaining about the burden of certificates. Will this finally drive an alternate solution such as Moxie Marlinspike's Convergence project to help us do away with the certificate authorities? Also, I can see a huge increase in the number of IP addresses unless some serious progress is made with SNI. On the otherhand, that might finally open the floodgates for widespread IPv6 adoption.
I'm a little unclear on how SPDY works. Is it correct that it only speeds up HTTPS connections? Does that mean you need to redirect traffic for:<p><a href="http://example.com/" rel="nofollow">http://example.com/</a><p>to:<p><a href="https://example.com/" rel="nofollow">https://example.com/</a><p>before you know if the client has SPDY support enabled?
Kinda crummy article to mention that SPDY is actually present in earlier Firefox versions, but just turned off. How about telling us how we can turn it on?