Re: RM - Definition needed!

[Arvola Chan <arvola@tibco.com>]

Ian:

I don't quite agree with the second part of your statement:

  "..., it has nothing todo with the quality, existence or number of
intermediate
  nodes in the path."

How reliable messaging between the sending MSH and target MSH can be
achieved (i.e., implemented) will very much depend on whether there are
intermediaries in between, and the quality of service they can support.

I still think that the approach taken in the 0.93 version of the spec, i.e.,
dividing the specification into

1. Single-hop reliable messaging
2. Multi-hop reliable messaging without intermediate acknowledgements (i.e.,
    none of the intermediaries adopt the reliable messaging behavior)
3. Multi-hop reliable messaging with intermediate acknowledgements (i.e.,
all
    of the intermediaries adopt the reliable messaging behavior)

is the right way to go. Cases 1 and 2 are straightforward to implement. Case
3 is the only that requires some work, but I think it can be solved without
some
of the complexities that David Burdette has introduced in his recent
proposal.

-Arvola

-----Original Message-----
From: ian.c.jones@bt.com <ian.c.jones@bt.com>
To: ebxml-msg@lists.oasis-open.org <ebxml-msg@lists.oasis-open.org>
Date: Thursday, August 16, 2001 9:21 AM
Subject: RM - Definition needed!


>It has been suggested that a useful step in the RM discussion is a simple
>BUT succinct definition of what RM means.  I agree that this would be
useful
>to "scope" the discussion as many other issues tend to drift in and out of
>this topic.
>
>As a start to the discussion to define in 1 paragraph or less - I would
like
>2 or at most 3 sentences, the start is:
>"RM is a protocol between the sending and target MSHs to get an indication
>that a message was delivered to the far end... pointedly, it has nothing to
>do with the quality, existence or number of intermediate nodes in the
path."
>
>This is a slightly re-worded contribution for an external party but I think
>encapsulates the sort of definition we need.
>
>Comments !!
>
>Ian Jones
>Chair OASIS ebXML Messaging Services TC
>
>Tel:  +44 (0)29 2072 4063
>Fax: +44 (0)29 2045 8781
>Email: ian.c.jones@bt.com
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>