- From: Haugen Robert <Robert.Haugen@choreology.com>
- Date: Tue, 16 Nov 2004 13:44:38 -0000
- To: <public-ws-chor@w3.org>
Nick, Unless I can't read, your latest lifeline proposal does not respond to the finalization issue, as expressed by Peter in the "original message" beneath your proposal: > ...the Life-line section needs to say something about > a choreography's "life after death" - or rather > finalization after completion... Note that this issue exists whether or not our multiple-finalizer proposal succeeds. What it means is that, if any finalizers have been defined for a choreography, the state that is now called "complete" is more accurately called something like "ready for finalization" - that is, the finalizer(s) is(are) enabled, the states of variables must be preserved, and external observers cannot know the final outcome of the choreography until a finalizer is fired, which may take a relatively long time. I added some language to the lifeline section about finalization to Coordination Proposal 3: http://lists.w3.org/Archives/Public/public-ws-chor/2004Oct/0066.html "After a Choreography completes successfully, any Finalizer blocks specified in the Choreography are enabled. In other words, as long as Finalizer blocks are enabled, the Choreography is still alive until one of the enabled Finalizers is fired and completes its own Work Unit, at which time the Choreography is closed." If I understood correctly, you didn't like "still alive", and I would prefer "ready for finalization" to "completed successfully", but the idea is there. Choreology Anti virus scan completed
Received on Tuesday, 16 November 2004 13:45:10 UTC