|
Hi Dmitri,
It's not possible at present to do something exactly like OTS implicit mode - but you can get close now, and perhaps closer later with a minor client side change.
Every method invocation has an associated calling context which is used to provide meta-data for the invocation. This is what we had in mind for, among other things, providing OTS support.
On the client side the application writer would provide a context with a parameter that identifies the OTS context (transaction id, etc). If we added support for a default context this would then be quite similar to implicit passing of the OTS context.
On the server side it is possible to interrogate the context in a servant locator. This means that the servant locator could implicitely associate the transaction id with the calling thread in the incoming path of the invocation, and tear down the association in the outgoing path. Freeze uses a technique very similar to this to provide the automatic persistence.
Regards, Matthew
|