Microsoft Wants Faster Internet With "HTTP Speed+Mobility"
Microsoft is submitting its own solution for HTTP 2.0 called HTTP Speed+Mobility.
Microsoft plans to submit a proposal for a faster internet protocol to the Internet Engineering Task Force (IETF) -- the standards body currently in charge of producing the second-generation Hypertext Transfer Protocol (aka HTTP 2.0) -- called HTTP Speed+Mobility. The IETF is currently meeting this week to discuss the future of HTTP which may also consider Google's next-generation solution called SPDY (pronounced speedy).
Microsoft revealed its plans on Sunday in a blog, reporting that HTTP Speed+Mobility will emphasize performance improvements and security while at the same time accounting for the important needs of mobile devices and applications. That means not only should browser-based surfing get faster, but mobile apps too, as they're how people access web services in addition -- sometimes in place of -- web browsers.
"Improving HTTP should also make mobile better, particularly to ensure great battery life and low network cost on constrained devices," reads the draft submitted to the IETF. "People and their apps should stay in control of network access. Finally, to achieve rapid adoption, HTTP 2.0 needs to retain as much compatibility as possible with the existing Web infrastructure. Done right, HTTP 2.0 can help people connect their devices and applications to the Internet fast, reliably, and securely over a number of diverse networks, with great battery life and low cost."
The draft refers back to Google's separate submission SPDY which actually replaces the HTTP protocol. It handles the same tasks, but does so 50-percent faster. Google's Chrome and Mozilla's Firefox already support SPDY, and several large websites -- including Google and Twitter -- dish out pages over SPDY where possible. Microsoft says its proposal builds on both the Google SPDY protocol, and the work the industry has done around the HTML5 WebSockets API.
"SPDY has done a great job raising awareness of web performance and taking a 'clean slate' approach to improving HTTP to make the Web faster," writes Microsoft’s Jean Paoli, General Manager of Interoperability Strategy . "The main departures from SPDY are to address the needs of mobile devices and applications."
Over on Google+, SPDY co-inventor Mike Belshe said that he welcomes Microsoft's IETF submission, saying that the company has a great crew of engineers and that their help in this problem space is "awesome" for the web.
"In their post, they imply that SPDY is not optimized for mobile, which is not true, he said. "SPDY is now over 3 years in the making with a lot of implementation knowledge and deployment expertise on both desktops and mobile. My current company, Twist, is a mobile apps company, and we're optimizing our mobile performance using SPDY. Given what other implementors have said about SPDY and mobile, I'd say its working pretty well. But it could always be better, of course."
"If Microsoft has some new ideas that prove to work, that's fantastic," he added. "The goal is not to take one vendor's implementation, but to aggregate the best concepts together and make the best protocol we can. I look forward to engaging more with Microsoft soon."
The IETF will likely take the best ideas out of all submissions and create a hybrid that's best for HTTP 2.0. There's a good chance we'll still type HTTP in our address bars for a while because that's what Web surfers have done for almost seventeen years.
What are you talking about? Microsoft software is amazingly secure, 99% of issues come from user error/idiocy.
What are you talking about? Microsoft software is amazingly secure, 99% of issues come from user error/idiocy.
Now let's see if anyone else use the feature. An unused feature is a dead feature, kinda like Rambus's DDR memory. No CPU or GPU manufacturer is using it, even AMD isn't using the XDR2.
And Google is? Are you writing from the early 90's? Or just from those that.. you know are just generally stuck with the opinions they are "raised" with?
Then again, If Microsoft gets their way, the Internet might just turn into a Windows Vista disaster.
Google isn't so bad, they pay people big bucks to find security flaws. Then again, wouldn't any company want the consumer to think positive about its mission?
Even Google is happy that MS is participating in this discussion and is bringing ideas to the table, yet the trolls keep perpetuating their nonsense.
Not that it matters, speed improvements will be nothing once the MPAA gets their deep packet sniffer in place at taxpayer expense to inspect every bit of data to see if they can claim it.
1.(E) Does it make us extraordinary?
2.(M) Does it matter to customers?
3.(B) Does is break new ground?
4.(E) Does it encourage evolvement?
5.(R) Is it real?
Of course, one should always hold MS accountable for the failure of OTHER COMPANIES to adjust to newer browser versions. If they didn't know didly squat about web standards then the latest versions of IE would still suck, and that clearly isn't the case. IE9 rocks and 10 is allegedly even better, with parity on supporting the not even close to finalized HTML5 "standard".
You can argue all day that IE6 sucked and you would most likely be right, but to say that MS doesn't know crap about web standards when their latest browsers are excellent and highly standard compliant is asinine.
Google managed to implement their protocol on two websites. Wow!
MS has the ability to add it to their web server and have instant implementation on millions of sites.
IE9 drags just as slow as ie6, in fact ie6 beats it out on a side by side comparison.
do you really want microsoft to be the sole designer when they have so many problems they don't do anything to fix what's broke or left with an open window policy that it takes thousands of people screaming at them to get them to fix it or would you rather have a company with a track record who pays for bugs hackers find in order to fix them before they become an issue even a few hundred scream about?
just judge on microsofts piss poor track record and performance. i know new versions of chrome and firefox work on older microsoft operating systems that can't upgrade past ie6 or ie8. and yet microsoft can't fix the older IE's let alone make a new IE that works for 98 or xp. how long before an IE that doesn't work on vista i give microsoft 2 years to pull that stunt on vista users 5-7 more years on windows7 users. that is how microsoft track record works.