[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: i030 proposed resolution
All, The following is a proposed resolution to i030, to allow an RMD to effectively ignore an offered sequence yet at the same time, provide for the RMS to know when it can safely reclaim the resources with the "unused" offered Sequence. Since i001 has already been resolved [2], it is not necessary to address that aspect (whether the wsrm:Offer is required under certain circumstances). All that is left to address is how to provide the RMS with an indication that the offered Sequence is being ignored by the RMD. Proposal: Remove lines 545-546 of WS-RM spec (pdf) [3] so as to not require that the RMD send a wsrm:Accept in a CSR for a CS with a wsrm:Offer. Absence of a wsrm:Accept in a CSR for a corresponding CS with wsrm:Offer enables the RMS to safely reclaim the resources associated with the offered sequence. It isn't clear to me that the spec need to say anything about that, but if some would prefer it did, I offer this addendum to my proposal to be inserted immediatly following the deleted lines above: Note: If a wsrm:CreateSequenceResponse is returned without a child wsrm:Accept in response to a wsrm:CreateSequence that did contain a child wsrm:Offer, then the RM Source MAY immediately reclaim any resources associated with the unused offered Sequence. [1] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14682/ReliableMessagingIssues.xml#i030 [2] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14682/ReliableMessagingIssues.xml#i001 [3] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14603/wsrm-1.1-spec-wd-03.pdf Cheers, Christopher Ferris STSM, Emerging e-business Industry Architecture email: chrisfer@us.ibm.com blog: http://webpages.charter.net/chrisfer/blog.html phone: +1 508 377 9295
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]