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

Re: Action Item - Part I: WSRX and MEP signaling on the wire

From: Mark Baker <distobj@acm.org>
Date: Wed, 4 Jan 2006 21:03:27 -0500
Message-ID: <c70bc85d0601041803i6a26c800ycfc437f6aa252b94@mail.gmail.com>
To: David Hull <dmh@tibco.com>
Cc: xml-dist-app@w3.org

On 1/4/06, David Hull <dmh@tibco.com> wrote:
>  The reliability standards I've seen distinguish between submit/deliver and
> transmit/receive.

i.e. they distinguish between transfer and transport (respectively).

>  The upshot here is that, even if I use a TCP-based transport, and even if
> that transport allows for status codes or some other indication of a
> successful exchange, successful transmission of a message does not imply
> successful delivery.

If it's a transfer protocol, that's *exactly* what it implies.

Sorry for my terseness, but I'm simultaneously bleeding from the ears,
pulling out my hair, and gritting my teeth, wondering why oh why folks
continue to treat application protocols like HTTP as transport
protocols, when what you clearly need *is* a transfer protocol!!

Mark.
--
Mark Baker.  Ottawa, Ontario, CANADA.       http://www.markbaker.ca
Coactus; Web-inspired integration strategies  http://www.coactus.com
Received on Thursday, 5 January 2006 02:03:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:21 GMT