|
Guy, welcome back. I think many of your questions
are moot with the changes that were made at the New Orleans face-to-face.
Hopefully we'll be making a version 0.3 of the doc available soon, but if you
read the minutes then you should see what the main differences will be. With
that in mind, some brief comments:
The 0.2 spec of CTX spec still has some elements that are confusing
(not sure if this has been discussed before, apologies if so).
Point
1:
What happens if there are both security and transaction contexts for the
same activity (if this is possible at all)?
Will they appear as two
different context headers or will they be nested within each
other?
That will be up to the using specification.
WS-Context has never said how different protocols must define their context
formats. In the next revision this should be even more explicit.
Point 2:
The clarification text defines an activity as
operations being executed within a valid context (or something similar)
(fine). A context can only belong to one activity (fine).
But if there can
be multiple contexts for one particular activity, which context is the one
that actually _defines_ the activity (and, consequently, its
outcome)?
There can only be one context per activity. The
context is the "physical representation" of the abstract notion of an activity.
How do you envision multiple contexts?
Point 3:
The text also states that if a context is used to
represent an activity, its context ID must be the activity ID.
This seems
to suggest that an activity can exist without a context, which contradicts the
activity definition from Point 2 ?
I think it's the fact that the activity id must be
the context id :-)
Mark.
----
Mark Little,
Chief Architect,
Transactions,
Arjuna Technologies Ltd.
www.arjuna.com
Thanks for any
clarification,
Guy
Dr. Guy Pardon ( guy@atomikos.com
)
Atomikos: Your Partner for Reliable eBusiness
Coordination
http://www.atomikos.com/
The information in this email
is confidential and only meant for the addressee(s). The content of this email
is informal and will not be legally binding for Atomikos.
|