Slashdot Mirror

← Back to Stories (view on slashdot.org)

HTTP's Days Numbered

Posted by ryuzaki0 on from the big-number-or-small-number-is-the-question dept.

dlek writes: "ZDNet is running an article in which a Microsoft .Net engineer declares HTTP's days are numbered. (For those of you just tuning in, HTTP is the primary protocol for the world-wide web.) Among the tidbits in this manifesto is the inference that HTTP is problematic primarily because it's asymmetric--it's not peer-to-peer, therefore it's obsolete. Hey everybody, P2P was around long before Napster, and was rejected when client-server architecture was more appropriate!"

2 of 505 comments (clear)

  1. Re:He's got a point by DohDamit · · Score: 0, Flamebait

    A few months? Well, that explains why you don't know a fucking thing about server-side scripting, the different methods of moving data around in forms, javascript, and plug-in's. Hey scoobie, there's more than just plain HTML out there!

  2. Re:Yeah, but by erasmus_ · · Score: 2, Flamebait

    Why post comments when you have absolutely no idea about the topic matter? Let's see, .NET is not built on SOAP, you're not even comparing anything that can be compared. .NET is a framework and a set of tools, whereas SOAP is a standard for XML data interchange. .NET applications can utilize SOAP, but saying that it's built on it is completely upside down.

    Next, let's discuss Microsoft realizing that .NET is a "stupid idea." Microsoft doesn't care about setting up a scapegoat because they're 100% sure it will work, and they're probably right. The whole company has been restructured to work with .NET and it is not going away. Latest copy of Windows in development is Windows.NET, latest set of development tools is Visual Studio.NET, latest certification is MCSD.NET. Getting a trend here yet?

    HTTP is old and needs to be replaced, as soon as we can figure out what the best replacement is. It will be extremely hard, just like IPv4 was, but very similarly, we had no idea the protocol would be used as it is being used today when it was developed. Microsoft is expressing something many other people know in this case, and the fact that a .NET architect said this does not really have anything to do with .NET, as this HTTP replacement would not happen for a long long time from now.

    I hope that addresses all your points, and educates you more about the subject at hand.

    --
    Please subscribe to see the more insightful version of th