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: [ws-rx] PR022: strawman proposal


Title: PR022: strawman proposal
+1


From: Gilbert Pilz [mailto:gpilz@bea.com]
Sent: Thursday, December 14, 2006 12:49 AM
To: ws-rx@lists.oasis-open.org
Cc: Hal Lockhart
Subject: [ws-rx] PR022: strawman proposal

From previous discussions on this issue it is evident that the TC doesn't think that the motivating requirement is pressing enough to justify any large changes to the spec (i.e. making TerminateSequence or CloseSequence required). With that in mind I propose that we resolve this issue by doing the following:

1.) Adding the mandatory LastMsgNumber element to CloseSequence. As previously discussed, the description of LastMsgNumber should be something along the lines of:

The LastMsgNumber element specifies the highest assigned message number of all the Sequence Traffic Messages for the Sequence being closed. The RM Destination can use this information, for example, to implement the behavior indicated by wsrm:CreateSequenceResponse/wsrm:IncompleteSequenceBehavior.

2.) The use of CloseSequence remains optional. Any agreement between the RMS and the RMD about the use of CloseSequence to allow the RMD to determine if it has succesfully received all the messages sent by the RMS is out of scope.

3.) An RMS that sends a CloseSequence but does not receive a CloseSequenceResponse is free to retry the CloseSequence message or not depending upon local policy etc.

- gp



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