W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > May 2010

[Bug 9607] Transfer: Support for WS-Management's RequestEPR feature

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 May 2010 21:44:53 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1OBxG1-00053o-4X@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9607


Tom Rutt <tom@coastin.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tom@coastin.com




--- Comment #3 from Tom Rutt <tom@coastin.com>  2010-05-11 21:44:52 ---
Proposed Response to Originator of Bug 9607

The WS-RA WG  have reviewed your review comment 9607, Transfer: Support for
WS-Management's RequestEPR feature, and have decided to close with no change.

Our rationale is as follows:

This is a broader issue, in that it affects more that ws-transfer Put.  
There are several operations over a network which could also result in 
such an EPR Change - as such this an issue that is bigger than 
what WSRA is chartered to work on.

For example, if a transfer put induced state change on a resource 
results it a change of its epr, then that same epr might change 
due to state changes due to other stimuli associated with the resource.

In such an environment, we suggest that using an specific event report
notification, perhaps defined as part of WS-Management, such as 
"state change induced EPR change" , would be a better solution.

Using a notification would allow all parties which need to track EPR 
changes to register for receiving that event report.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 11 May 2010 21:44:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 May 2010 21:44:54 GMT