Re: The deep difference between request/response andfire-and-forget
Rich Salz <[email protected]>
| Newsgroups | gmane.text.xml.distributed |
|---|---|
| Message-ID | <[email protected]> |
> 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 wrong. /r$ -- SOA Appliance Group IBM Application Integration Middleware * This address is going away; please use [email protected] *