W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2006

Re: The deep difference between request/response andfire-and-forget

From: Rich Salz <rsalz@datapower.com>
Date: Fri, 27 Jan 2006 11:59:15 -0500
Message-ID: <43DA5163.9020807@datapower.com>
To: David Hull <dmh@tibco.com>
CC: xml-dist-app@w3.org

> I'm also concerned about protocols like XMPP <message/>, which provide a 
> one-way transactional operation.  That is, IIUC, you can tell whether 
> your <message/> arrived or not even if you're not expecting a response.

I don't think so.  If the TCP layer detects a failure and reports it 
back up to the next layer, you have no way of knowing how many bytes of 
any pending messages were actually received at the other side.

This is a limitation of any TCP-based protocol -- the layer using TCP 
needs to have an explicit ACK.  TCP is reliable as long as nothing goes 


SOA Appliance Group
IBM Application Integration Middleware
* This address is going away; please use rsalz@us.ibm.com *
Received on Friday, 27 January 2006 16:56:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:29 UTC