This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

WS-ReliableMessaging and DeliveryAssurances

Stefan Tilkov,

Continuing my investigation of WS-ReliableMessaging, I am puzzled by a spec change that occurred from the March 2003 version to the current one released in March 2004. Both specs mention different delivery assurances in the introduction — AtMostOnce, AtLeastOnce, ExactlyOnce, and InOrder. The old spec contains details how these delivery assurances are specified (in section 4.2); the new spec drops this whole section, and adds the following sentence to the introduction:

Persistence considerations related to an endpoint’s ability to satisfy the delivery assurances defined below are the responsibility of the implementation and do not affect the wire protocol. As such, they are out of scope of this specification.

I understand the reason for defining this to be out of scope of the WS-ReliableMessaging spec. It also seems to address one of the clarity issues Dave Chappell wrote about last year.

I totally fail to see why they delivery assurances, including their technical, spec-suggesting name, are still part of the new spec and not removed altogether. Any hint, as well as some rationale about this spec change in general, would be greatly appreciated.

On April 20, 2004 3:49 PM, Chris Ferris said:

See my response.

On April 20, 2004 3:50 PM, Chris Ferris said:

grumble… take 2. See my response here: