Hi, I'm currently working on multiple response support for the comet binding. I have an initial implementation but I'm using the thread context to store some internal state between forward and callback calls and this leads to some limitations. So I was thinking that something similar to @Conversational from Tuscany 1.x would improve scalabilty as storing state does not depend on the thread context anymore.
To be more precise, for each client an object is created server-side and it has to be accessible from the Invoker when performing a callback call. At the moment, I'm passing this object through the bindingContext property of the Message. When performing the callback call, the callback message is built by copying most of the properties of the ThreadContext Message so I added a slight modification to the core which copies the bindingContext as well. If it's possible, I'd like to be more thread context independent and conversational scope seems to provide this thread-neutral client-specific storage space. It would also enable me to make async invocation of the service implementation. Could you point me out a way to achieve something similar to @Conversational in Tuscany 2.x? From Tuscany In Action I found out that "conversations aren’t included in the SCA 1.1 specifications being defined by OASIS and will be reconsidered for a future version of SCA. They’re supported in the Tuscany SCA 1.x codebase but not in Tuscany 2.x". Thanks, Florian
