Re: [ws-rx] NEW ISSUE: Remove LastMessage

[Paul Fremantle <paul@wso2.com>]

Doug

I think this makes a lot of sense. One of the biggest problems in 
implementation is that programmers rarely know when a message is a last 
message.

Paul

Doug Davis wrote:
>
> Title:Remove LastMessage
>
> Description:
> The LastMessage element, as part of a Sequence header element, appears 
> superfluous. It seems to serve 2 purposes:
> 1 - force a SeqAck to be sent back from the RMD
> 2 - force the RMD to reject any messages with a higher message #
>
> #1 can be done with an AckReq header.  We should avoid having multiple 
> ways to do the same thing.
> #2 is really only an issue if someone tries to hijack the sequence - 
> and to protect against that we should be using a real security 
> mechanism like WS-SC/Trust, not the LastMessage element.
>
> When an RMS is done with a sequence it is free to simply Close or 
> Terminate it (whether or not it has all of the Acks it wants - but 
> normally it will wait) - having an additional message exchange to send 
> a LastMessage is unnecessary.
>
> Justification: See above.
>
> Target: core
>
> Proposal:  Remove all references to LastMessage (and related Fault) 
>  from the spec [1].  See attached diff/pdf file for the specific changes.
>
> [1] 
> http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/15001/wsrm-1.1-spec-wd-05.pdf 
>
>
>
> Note the protocol flow/example picture was updated too. 


-- 

Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
"Oxygenating the Web Service Platform", www.wso2.com

Yahoo IM: paulfremantle
VOIP: +44 844 986 2874
Cell/Mobile: +44 (0) 7740 199 729
Fax:  +44 844 484 7459 
paul@wso2.com