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: RE: [ebxml-msg] Re: Comments on the 1.09 about ConversationId


OK, done.

David.

-----Original Message-----
From: Christopher Ferris [mailto:chris.ferris@sun.com]
Sent: Friday, December 07, 2001 8:30 AM
To: Doug Bunting
Cc: ebxml-msg@lists.oasis-open.org
Subject: Re: [ebxml-msg] Re: Comments on the 1.09 about ConversationId


None at all.

Doug Bunting wrote:

> Shimamura-san,
> 
> Yes, that's what I'm proposing.
> 
> Chris,
> 
> This was your suggestion, do you mind removing the complexity?
> 
> Team,
> 
> What do you think we're losing if we remove the ability to use
> SequenceNumber with NotGuaranteed behaviour?  Put another way, do we foresee
> sliding-window (per-conversation not per-sender) Reliable Messaging
> implementations that don't turn the messages over to the application in
> order?
> 
> thanx all,
>     doug
> 
> ----- Original Message -----
> From: "SHIMAMURA Masayoshi" <shima.masa@jp.fujitsu.com>
> To: "Doug Bunting" <dougb62@yahoo.com>; <chris.ferris@sun.com>
> Cc: <ebxml-msg@lists.oasis-open.org>
> Sent: Thursday, 06 December 2001 02:31
> Subject: Re: Comments on the 1.09 about ConversationId
> 
> 
> Doug and Chris,
> 
> On Wed, 05 Dec 2001 09:06:23 -0800
> Doug Bunting <dougb62@yahoo.com> wrote:
> ...
> 
>>I recommended, in my comments on the schema and the second half, removal
>>
> of
> 
>>the messageOrderSemantics attribute and requiring SequenceNumber in
>>MessageOrder.  The current module is more complicated than necessary,
>>
> 
> I think that the Doug's change proposal about MessageOrder means:
>     - When MessageOrder element appears, message order is guaranteed. If
>       it does not appears, message order is not guaranteed.
>     - The MessageOrder element has always SequenceNumber element inside.
> Is that correct, Doug?
> 
> In the current specification (v1.09), SequenceNumber may appear even if
> MessageOrderSemantics is set to NotGuaranteed so that receiving
> application can use the SequenceNumber to guarantee message order by
> itself. I think it was Chris's idea. See:
>    http://lists.ebxml.org/archives/ebxml-transport/200103/msg00099.html
>    http://lists.ebxml.org/archives/ebxml-transport/200103/msg00101.html
>    http://lists.ebxml.org/archives/ebxml-transport/200103/msg00102.html
>    http://lists.ebxml.org/archives/ebxml-transport/200103/msg00104.html
> 
> Doug's change proposal removes the feature. Chris, what do you think?
> 
> 
> 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
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
> 



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>



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


Powered by eList eXpress LLC