[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: activity context
Yes, it would be good if we could make progress on the context format.
The basic structure could pass common features (such as the coordinator
reference, timeout etc) in a strongly types fashion, and we can then allow model
specific data in a less strongly typed manner (e.g., a CORBA any in the
example), because any user of that data must check the type structure of the
context anyway.
Agreed. There's nothing to say that the model specific data couldn't be
encrypted, for example.
I think that the general context should be a series of specific context
instances, one for transactions (which only talks about transaction related
stuff), one for security, etc.
Agreed. Do you know where the W3C is with this at the
moment?
All the best,
Mark.
----------------------------------------------
Dr. Mark Little (mark@arjuna.com) Transactions Architect, HP Arjuna Labs Phone +44 191 2064538 Fax +44 191 2064203 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC