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] question about QoS


FYI

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

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/07/2001
09:15 AM ---------------------------

Martin W Sachs
12/07/2001 09:14 AM

To:    David Fischer <david@drummondgroup.com>
cc:
From:  Martin W Sachs/Watson/IBM@IBMUS
Subject:    RE: [ebxml-msg] question about QoS  (Document link: Martin W.
       Sachs)

I completely agree with renaming it. Not only is there only one piece of
information but reliable messaging attributes are not part of what is
usually called quality of service (system availability, performance
guarantees, etc.)

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



David Fischer <david@drummondgroup.com> on 12/06/2001 06:53:58 PM

To:    ebxml-msg <ebxml-msg@lists.oasis-open.org>
cc:
Subject:    RE: [ebxml-msg] question about QoS




To the team,

Does anyone object to renaming QOS to  DuplicateElimination?

Regards,

David Fischer
Drummond Group
ebXML-MS  Editor.
-----Original Message-----
From: Arvola Chan  [mailto:arvola@tibco.com]
Sent: Thursday, December 06, 2001 5:48  PM
To: Cliff Collins; ebxml-msg
Subject: Re: [ebxml-msg]  question about QoS


Cliff:

Please see my comments inline.

-Arvola
-----Original Message-----
From:  Cliff Collins <collinsc@sybase.com>
To:  ebxml-msg <ebxml-msg@lists.oasis-open.org>
Date:  Thursday, December 06, 2001 3:24 PM
Subject: [ebxml-msg]  question about QoS


I have 2  questions/comments about the recent talk regarding
QualifyOfService and  DuplicationElimination.

1. It was said  that QoS with DuplicationElimination must be present in
every message. Does  this include MSH types messages where
DuplicationElimination would never be  true? i.e.
ping/ping/StatusRequest/StatusResponse/Acknowledgements must also  include
QoS with DuplicationElimination =false.

<ac>
The QoS element with the duplicateElimination  attribute set to "true"
needs to be included in the message header only if  duplicate elimination
is desired. It is quite pointless to include a QoS  element with
duplicateElimination set to "false".
</ac>

2. Since  QualifyOfService only contains one attribute
(DuplicationElimination) why  not rename the "QualifyOfService" element to
"DuplicationElimination"? This  would also mean that question #1 above
wouldn't make sense. This element  would only appear when
"DuplicationElimination" is true. This would be more  in line with other
elements like "AckRequested" and "SyncReply". IMO leaving  QualifyOfService
the way it is seems inconsistent with the rest of the  spec.

<ac>
I agree with you that it will be more  consistent if we rename the QoS
element the DuplicateElimination element and  to do away with the embedded
duplicateElimination attribute.
</ac>

Cliff Collins
mailto:collinsc@sybase.com
URL: http://www.skyweyr.com/cliff
(510)922-5204








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


Powered by eList eXpress LLC