conversational callbacks
is to allow a callback invocation to occur on a client component
instance that contains state that existed when the correspon-
ding forward invocation went out. This to me means that the
client component instance behaves as a conversational ser-
vice
On Jan 8, 2007, at 8:18 AM, Ignacio Silva-Lepe wrote:
Hmm, the premise of your scenarios is actually what I am trying
to figure out. In either of the two scenarios you assume that C's
contract is conversational. C's contract with whom?
I have a feeling we are not using the same terminology and
Ok, so we are agreeing that C has a (service) contract with T
by virtue of the callback interface (that defines cb1), and that
contract is conversational and it does not pertain to any
other client.
You are also saying that the conversation id to be used by
m1 to set up state, and by cb1 to use
.
Yes as an implementation strategy.
On 12/20/06, Jim Marino [EMAIL PROTECTED] wrote:
On Dec 19, 2006, at 8:12 AM, Ignacio Silva-Lepe wrote:
I'm assuming the goal of supporting conversational callbacks
is to allow a callback invocation to occur on a client component
instance that contains
the goal of supporting conversational callbacks
is to allow a callback invocation to occur on a client component
instance that contains state that existed when the correspon-
ding forward invocation went out. This to me means that the
client component instance behaves as a conversational ser
invoker tries to retrieve the instance of C, which may need
some collaboration by cb1's callback invocation handler.
On 12/20/06, Jim Marino [EMAIL PROTECTED] wrote:
On Dec 19, 2006, at 8:12 AM, Ignacio Silva-Lepe wrote:
I'm assuming the goal of supporting conversational callbacks
is to allow
On Dec 19, 2006, at 8:12 AM, Ignacio Silva-Lepe wrote:
I'm assuming the goal of supporting conversational callbacks
is to allow a callback invocation to occur on a client component
instance that contains state that existed when the correspon-
ding forward invocation went out. This to me means
I'm assuming the goal of supporting conversational callbacks
is to allow a callback invocation to occur on a client component
instance that contains state that existed when the correspon-
ding forward invocation went out. This to me means that the
client component instance behaves
