- From: Cahill, Conor P <conor.p.cahill@intel.com>
- Date: Wed, 7 Dec 2005 08:42:59 -0800
- To: <tom@coastin.com>
- Cc: "David Hull" <dmh@tibco.com>, "John Kemp" <john.kemp@nokia.com>, "ext Yalcinalp, Umit" <umit.yalcinalp@sap.com>, <public-ws-addressing@w3.org>
> > My example was more along the lines of a persistent TCP connection > > across which multiple requests and responses were sent > without regard > > for direct pairing/sequencing of the responses. > > I am confused, I thought if you put http request on a tcp > connection, you cannot send the next http request until the > http response is received for the previous request (http pipelining). I wasn't anticipating the use of HTTP for such a connection as I think there would likely be problems trying to do bi-directinaly messaging (which you need to do for asynchronous messaging without polling) on an HTTP connection. You can use HTTP for asynchronous messaging if you are using independent channels for requests & responses at the SOAP layer, but that would be a non-anonymous reply address in the requests. Conor
Received on Wednesday, 7 December 2005 16:45:04 UTC