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


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

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

Subject: RE: Issue i098 - This is about protocol vs. sequence faults

I guess I don't understand the opposition of "protocol vs. sequence". In my mind an InvalidAcknowledgement is certainly a "protocol fault" (as in, "Dude, you're not following the protocol 'cause you acknowledged something I never sent you!"). It is also a "sequence-related fault" in that the invalid acknowledgements included a <wsrm:Identifier> that identified a valid sequence (otherwise the RMS would presumably have sent an UnknownSequence fault).
All the faults defined by WS-RM are "WS-RM protocol faults". Some of these faults relate to a particular sequence. Some of these faults do not.
- gp

From: Marc Goodner [mailto:mgoodner@microsoft.com]
Sent: Tuesday, March 07, 2006 9:11 AM
To: Gilbert Pilz; ws-rx@lists.oasis-open.org
Subject: Issue i098 - This is about protocol vs. sequence faults

The issue says “sequence” and “non-sequence” faults, I would characterize it more as protocol vs. sequence faults though.


I agree that the text referred to is garbled, I think the editor may have already made a change to that text to try to improve it. If so could one of the editors provide that to the list so we can discuss this with the most recent language in the spec?


It seems to me that if this text is fixed, i.e. that it is referring to protocol operation faults, that is probably sufficient. Are you suggesting that more needs to be done? For example do you think that every fault needs to be annotated in the spec as to whether it is a protocol or sequence fault?


Marc Goodner

Technical Diplomat

Microsoft Corporation

Tel: (425) 703-1903

Blog: http://spaces.msn.com/mrgoodner/


Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

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