From: Larry Masinter (firstname.lastname@example.org)
Date: Fri Aug 18 2000 - 08:55:34 PDT
> Proxies unilaterally disconnect long lived streams at a timeout, usually
> 5-15 mins. Without acks it is impossible for a sender to know which
> messages were sent but not received. So an http based protocol like SOAP
> has to support retransmission by numbering packets, caching them, setting
> some kind of ack, and manually doing reassembly. In other words, the
> browser assumptions of the infrastructure force us to reinvent TCP on top
> HTTP as if HTTP were IP, and that leads to a situation where we get TCP,
> except slow and buggy. bleh. bleh. bleh.
> This must have been discussed by hard core HTTPists like Roy F. Anybody
> know what the result was?
Proxies were an afterthought; SOAP doesn't consider them. Result:
SOAP over HTTP su... er, has technical difficulties.
You might be better off using SOAP over TCP and TCP over HTTP
This archive was generated by hypermail 2b29 : Fri Aug 18 2000 - 08:57:57 PDT