[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue 23: CreateSequenceRefused fault should apply to sender andreceiver
I believe we discussed this on a
call and I had an outstanding action to come back to the TC on why I thought
this was so. Currently the spec defines this
as a Sender fault, so I won’t talk to that. The reason it should also be
a receiver fault is that there may be times when the RMD that receives the CS
message may simply be incapable of initiating a new sequence. For example the
RMD may have no more capacity to process a request for an additional sequence. Therefore
if the same CS message is resent later it may be accepted making Sender the
wrong code in that instance. From: Marc Goodner
[mailto:mgoodner@microsoft.com] In section 4.6 the CreaetSequenceRefused fault is defined as
a sender fault. This fault should apply to sender or receiver. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]