Microsoft Wants to Kill HTTP?

by Jon Hall

(Based on an article in our News section below:)

Who said Web Services have to use HTTP? The leading standard for calling a web service that exists right now is SOAP, and SOAP does not specify a port to use. Nobody has said that regular web servers have to get and respond to Soap traffic... Either way, it was Microsoft's idea in the first place to require HTTP for Soap. Now they are saying it has limitations? That makes no sense. On top of it all, SOAP is just another way of saying RPC. So, MS's Soap protocol is XML-RPC's competition, and now MS is worried that RPC over HTTP is limited by HTTP??

The second part about P2P is them babbling about the way the web works. It's always been a stateless environment. Why the heck do we need both sides to initiate connections over HTTP? Do you want to be sitting on a website that all of the sudden opens a connection to your browser and starts sending something? As for HTTP not being interoperable, tell that to the Gnutella people. The entire Gnutella network uses HTTP, and it works great. There isn't really an overriding reason to use HTTP, but it's familiar and it works.

So what exactly is the problem with http?

• Subscribe
• RSS

• Editorial
• Specials
• Community
• News
• Tech and Tags
• Views
• Reviews
• Techniques
• Security
• Best of ColdFusion Talk
• Knowledge Base
• Blog Watch

• Tipical Charlie