Differences between revisions 1 and 2
Revision 1 as of 2006-07-03 12:01:44
Size: 729
Editor: jmarino
Comment:
Revision 2 as of 2009-09-20 22:47:49
Size: 726
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
This should be similar to [wiki:/LocalConversationalCallback Local conversational callback ] except invocations flow through references and services in a composite. As a start, we can create a simple socket-based binding that serializes Java objects along with a session id This should be similar to [[/LocalConversationalCallback|Local conversational callback ]] except invocations flow through references and services in a composite. As a start, we can create a simple socket-based binding that serializes Java objects along with a session id

Remote Conversational Callback

Description

The ability to invoke a service in a non-blocking fashion and receive a conversational callback over a remote binding.

Use cases

1. Simple socket-based binding

This should be similar to Local conversational callback except invocations flow through references and services in a composite. As a start, we can create a simple socket-based binding that serializes Java objects along with a session id

2. Use of extension bindings

Building on the first use case, we can flow invocations accross bindings handled by extensions such as Axis2 and Celtix. We may be able to flow session ids using WS-RM sequence ids.

Tuscany/TuscanyJava/Scenarios/ConversationalSupport/RemoteConversationalCallback (last edited 2009-09-20 22:47:49 by localhost)