[ebxml-msg] Re: Comments on the 1.09 about ConversationId

[Martin W Sachs <mwsachs@us.ibm.com>]

Sorry - I forget to reply to all.

*************************************************************************************

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
*************************************************************************************
---------------------- Forwarded by Martin W Sachs/Watson/IBM on 12/04/2001
08:56 AM ---------------------------

Martin W Sachs
12/04/2001 08:55 AM

To:    SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com>
cc:
From:  Martin W Sachs/Watson/IBM@IBMUS
Subject:    Re: Comments on the 1.09 about ConversationId  (Document link:
       Martin W. Sachs)

Shimamura-san,

If you add a status attribute, the application (or conversation management
middleware) still has to tell the MSH how to set that attribute.

You cannot ignore software errors.  You cannot guess at the correct
behavior.  A software error is an error and must be reported as an error.

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
*************************************************************************************



SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com> on 12/03/2001 10:16:18 PM

To:    Martin W Sachs/Watson/IBM@IBMUS
cc:    Dan Weinreb <dlw@exceloncorp.com>, ebxml-msg@lists.oasis-open.org
Subject:    Re: Comments on the 1.09 about ConversationId



Martin,

On Mon, 03 Dec 2001 09:30:35 -0500
Martin W Sachs <mwsachs@us.ibm.com> wrote:
>
> Shimamura-san
>
> If the conversation is managed by higher levels of middleware, then the
> receivng and sending MSHs still can know when the conversation is ended.
> It can find out through its own API from the middleware that manages the
> conversation.  These things are very hard to discuss and achieve
consensus

It seems not good idea. Because receiving application might forget to
notify receiving MSH of the end of conversation. If we add the status
attribute to ConversationId element, receiving MSH can know always when
the conversation is ended.


Regards,

--
SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com>
TEL:+81-45-476-4590(ext.7128-4241)  FAX:+81-45-476-4726(ext.7128-6783)
Planning Dep., Strategic Planning Div., Software Group, FUJITSU LIMITED