OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

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


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.


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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC