Re: [ws-rx-implement] TerminateSequence

[Doug Davis <dug@us.ibm.com>]

1 - I think you're ok to send the TS
to any of the EPRs (CS ReplyTo or app-level ReplyTo).
2 - I wonder if the TC really intended
for what's in the spec.  The spec says:

Upon receipt of this message, or subsequent
to the RM Destination closing the Sequence of its own volition, the RM
Destination MUST include a final SequenceAcknowledgement (that MUST include
the <wsrm:Final> element) header block on each message destined to
the RM Source, including the CloseSequenceResponse message and on any Sequence
Fault transmitted to the RMS. 

Notice that it doesn't place any restriction
on the type of message - so you're correct that it probably does apply
to the TerminateSequenceResponse but it could technically be read to mean
ALL messages even when they have nothing to do with RM at all.  We
should log this as a potential issue.

thanks
-Doug

"Ondrej Hrebicek" <Ondrej.Hrebicek@microsoft.com>

03/17/2006 01:09 PM

To	<ws-rx-implement@lists.oasis-open.org>
cc
Subject	[ws-rx-implement] TerminateSequence

Hi everyone,
 
I noticed two things in the scenarios document
as I was going through it last night:
 
1. Destination of RMD’s TerminateSequence
when Offer is used.
 
Since the RMD-to-RMS sequence gets created
and initialized before any application messages get sent, some implementations,
like ours, may set its protocol message destinations at that time. The
fact the TerminateSequence would be sent to an application message ReplyTo
thus causes a problem. Can we also add the CS ReplyTo as a potential destination
for the TS?
 
2. TerminateSequenceResponse not carrying
a final acknowledgement after CloseSequence was sent.
 
The spec says all messages that the RMD sends
to the RMS after it has received a CloseSequence must carry the final acknowledgement.
The scenarios doc doesn’t do this for the TerminateSequenceResponse in
the “gap” scenario. I can update it if there are no objections.
 
Thanks!
Ondrej