[Bug 226] New: Relevance of client-to-coordinator interactions

[bugzilla-daemon@arjuna.com]

http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=226

           Summary: Relevance of client-to-coordinator interactions
           Product: WS-CF
           Version: 1.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Model
        AssignedTo: ws-caf@lists.oasis-open.org
        ReportedBy: mark.little@arjuna.com
         QAContact: mark.little@arjuna.com


Now that WS-CF is moving towards a central notion of an activity group and 
pushing all coordinator protocol specific interactions to referencing 
specifications, the section on client-to-coordinator interactions looks out of 
place. To recap, what this allows for is a basic level of interaction at the 
WS-CF level between all coordinator implementations and all client 
implementations. All that a client can do is enquire of the state of the 
coordinator and trigger coordination "events", which may not be supported by 
all coordinators.

Furthermore, since we removed upcall operations from participant-to-
coordinator (allowing, for example, a participant to autonomously upcall its 
transition from one state to another without being triggered by an explicit 
coordinator message), this looks even more out of place.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.