This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 274 - Communication of State Change
Summary: Communication of State Change
Status: CLOSED WONTFIX
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Coord and alignment (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Steve Ross-Talbot
QA Contact:
URL:
Whiteboard:
Keywords:
: 318 (view as bug list)
Depends on:
Blocks: 333
  Show dependency tree / graph
 
Reported: 2003-07-15 09:47 UTC by Greg Ritzinger
Modified: 2005-01-04 20:34 UTC (History)
1 user (show)

See Also:

Attachments

Description Greg Ritzinger 2003-07-15 09:47:19 UTC 
How are state changes (e.g. new participant join) communicated? part of the 
choreography infrastructure or built into a choreography?
Comment 1 Martin Chapman 2004-01-08 14:06:28 UTC 
*** Bug 318 has been marked as a duplicate of this bug. ***
Comment 2 Martin Chapman 2004-03-04 05:54:39 UTC 
Requirement C-CR-4611 allows participant bndings to change at run-time - how 
are thse changes communicated to other parties in the choreography
Comment 3 Martin Chapman 2004-03-23 17:03:26 UTC 
coordination protocol discussed at http://lists.w3.org/Archives/Member/member-
ws-chor/2004Mar/att-0026/20040316-0.htm
Comment 4 Greg Ritzinger 2005-01-04 20:29:11 UTC 
SRT - This is probably not relevant and so should be marked as CLOSED 
WON'T FIX. But for clarity sake I would ask the owner of the issue what 
is meant by a "new" participant? And ask is this relevant any longer?