Just learnt about Microsoft’s S&M proposal. Horrible naming — almost like dark humour for journalists.
S&M vs. SPDY: Microsoft and Google battle over the future of HTTP 2.0
Lumbered with the truly awful name of HTTP Speed+Mobility, or HTTP S&M for short, Microsoft’s vision of HTTP 2.0 is mostly very similar to SPDY (and it admits as much on the Microsoft Interoperability blog), but with additional features that cater towards apps and mobile devices. “The HTTP Speed+Mobility proposal starts from both the Google SPDY protocol and the work the industry has done around WebSockets,” says Jean Paoli from the Microsoft Interoperability team. WebSockets in this case refers to a feature in HTML5 that allows websites (or indeed web apps) to open up bidirectional, real-time channels with remote servers over TCP, which is something that neither HTTP nor SPDY is capable of.
In short, the entire purpose of SPDY is to speed up the web — which isn’t a bad thing, and nor is it surprising, considering Google’s fanatical penchant for speed, but Microsoft is basically saying that speed isn’t everything. With HTTP Speed+Mobility, Microsoft is saying that we should also take into account factors such as battery life and bandwidth cost, both of which will play a big part in Windows 8 in specific and mobile computing in general.
Not exactly new news but still worth watching.