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: NEW ISSUE Editorial Create Sequence assumes both request and responseare received.


In WD 15 Section3.1 “Sequence Creation” it is stated starting at line 253

 

“The RM Source MUST request creation of an outbound Sequence by sending a CreateSequence

element in the body of a message to the RM Destination which in turn responds either with a message

containing CreateSequenceResponse or a CreateSequenceRefused fault.”

 

This does not account for the possibility that any of the CreateSequence, CreateSequenceResponse, or CreateSequenceRefused fault may have been lost in transit.

 

Proposal:

 

New text:

 

“The RM Source MUST request creation of an outbound Sequence by sending a CreateSequence

element in the body of a message to the RM Destination which in turn responds either with a message

containing CreateSequenceResponse or a CreateSequenceRefused fault.  In the event that the RM Source fails to receive either a CreateSequenceResponse or a CreateSequence fault in a timely manner then it MUST do either a) re-send the CreateSequence, or b) abandon the CreateSequence attempt and terminate the Sequence.  If the RM Destination received a CreateSequence that it has already processed such that the indicated Sequence exists, then it shall respond with a CreateSequenceResponse providing that there have been no messages in that sequence received and the state of that Sequence shall remain unchanged.  The RM Source SHALL NOT under any circumstances send any message to the RM Destination for a particular sequence until that Sequence has been successfully created as evidenced by the successful the receipt of a CreateSequenceResponse.  In the event that the RM Destination receives a CreateSequence for a Sequence that already exists and for which the RM Destination has already accepted messages, then the RM Destination shall respond with a Sequence Terminated fault as described in Section 4.2 and SHALL immediately terminate the Sequence”

 

 

State table impacts:

 

Add a two new row to the RM Destination state table as follows

CreateSequence (duplicate & empty)[msg]{3.1) | N/A | Send Create Sequence Response[Same] | Send Unknown Sequence Fault[Same]{4.3}

CreateSequence (duplicate & not empty)[msg]{3.1) | N/A | Send Sequence Terminated fault[None]] | Send Unknown Sequence Fault[Same]{4.3}

 

 

 



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