Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2006-07-03 09:50:05 →
Size: 623
Editor: jmarino
Comment:
← Revision 4 as of 2009-09-20 22:47:32 → ⇥
Size: 620
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:/LocalStatelessCallback Local stateless 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 This should be similar to [[/LocalStatelessCallback|Local stateless 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

Local Stateless Callback

Description

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

Use cases

1. Simple socket-based binding

This should be similar to Local stateless 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

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.

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