You need to say enough in the MSG spec to inform an implementer that
persistDuration follows different rules for conversationId and
last-ordered-message than for reliable messaging. Considering the amount
of discussion we have had on this point, we cannot assume that a
"reasonable implementer" will know what to do. There are plenty of examples
in the newspapers about deadly mistakes made by reasonable implementers.
The Risks Forum mut be full of them.
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
Christopher Ferris <chris.ferris@sun.com> on 12/04/2001 09:39:42 PM
To: David Fischer <david@drummondgroup.com>
cc: Martin W Sachs/Watson/IBM@IBMUS, Dan Weinreb <dlw@exceloncorp.com>,
ebxml-msg@lists.oasis-open.org
Subject: Re: [ebxml-msg] Re: Comments on the 1.09 about ConversationId
The thing I have trouble with here is why we have to say anything
in the spec. This is too suggestive of implementation detail
IMO (although probably accurate). Why do we need to say anything
about this at all?
Cheers,
Chris
David Fischer wrote:
> OK, I think that will work, but it is not the whole message which needs
to be
> saved. Once the message is delivered to the application, just the
MessageId,
> CPAId, persistDuration, ConversationId, SequenceNumber (did I get
everything?)
> need to be saved. The spec says now only the MessageId needs to be saved
but
> that's not enough for MessageOrder.
>
> David.
>
>