[Bug 84] State whether URI's are for dereferencing or identification

[bugzilla-daemon@arjuna.com]

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

mark.little@arjuna.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |LATER



------- Additional Comments From mark.little@arjuna.com  2004-04-15 10:44 -------
Text updated to:

"The context consists of the following items: 
•	A mandatory URI identifier called context-identifier. This guarantees 
global uniqueness for an individual activity (such an identifier can also be 
thought of as a “correlation” identifier or a value that is used to indicate 
that a task is part of the same work activity). Because contexts may be passed 
by reference or passed by value, the context-identifier may also refer to a 
Web service (the Context Manager) where the context resides, if it is passed 
by reference. In which case, the URI may be used as a Web service identifier 
to obtain the context and none of the other context elements will appear in 
the initial SOAP header.
•	An optional URI element, activity-service, which identifies the 
Context Service responsible for generating the context. This element may not 
be dereferenced and is only for unique identification.
•	An optional identifier that indicates the type of the activity 
(protocol-type). This element may not be dereferenced and is only for unique 
identification.
•	An optional list of the Application Web services currently 
participating in the activity, called participating-services.
•	An optional list of child activities, in the child-contexts element.
•	A timeout value, which indicates for how long the context information 
is valid; after this period has elapses, the activity to which the context 
refers to may no longer exist (e.g., the activity may be terminated and the 
structure garbage collected). This is to allow a Context Service 
implementation, in the event of no external stimulus, to terminate activities 
automatically rather than have them potentially run forever."



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