• To: xml-dev@l...
• Subject: MS thinks HTTP Needs Replacing???
• From: Mike Champion <mc@x...>
• Date: Tue, 26 Feb 2002 12:08:36 -0500

See
http://news.zdnet.co.uk/story/0,,t269-s2105076,00.html

'The protocol used to deliver Web pages has reached its limits for Web 
services and peer-to- peer applications, according to Microsoft .Net 
evangelist Don Box ...

Among the problems with HTTP, said Box, is the fact that it is a Remote 
Procedure Call (RPC) protocol; something that one program (such as a 
browser) uses to request a service from another program located in 
another computer (the server) in a network without having to understand 
network details.

This works for small transactions asking for Web pages, but when Web 
services start running transactions that take some time to complete over 
the protocol, the model fails. "If it takes three minutes for a response, 
it is not really HTTP any more," Box said. The problem, said Box, is that 
the intermediaries -- that is, the companies that own the routers and 
cables between the client and server -- will not allow single 
transactions that take this long."'

• Follow-Ups:
  • Re: MS thinks HTTP Needs Replacing???
    • From: Paul Prescod <paul@p...>
  • RE: MS thinks HTTP Needs Replacing???
    • From: "Leigh Dodds" <ldodds@i...>
  • RE: MS thinks HTTP Needs Replacing???
    • From: "David LeBlanc" <whisper@o...>

• Prev by Date: RE: Evaluating RPC versus REST
• Next by Date: RE: MS thinks HTTP Needs Replacing???
• Previous by thread: <OT> MaGIC
• Next by thread: RE: MS thinks HTTP Needs Replacing???
• Index(es):
  • Date
  • Thread