On Jul 10, 2006, at 7:40 AM, Jeremy Boynes wrote:
On Jul 10, 2006, at 7:19 AM, Jim Marino wrote:
2. We need to get the host API supporting callbacks. The reference
would use the host API to register itself as a listener with a
binding as opposed to talking directly with the binding. This will
allow us to decouple the callback infrastructure from particular
bindings. Jeremy may have some thoughts on this.
I would have though that the reference would register with the
binding rather than the host. After all the reference is bound on
the outbound side so is coupled to the binding at that point;
wouldn't the inbound side just be the reverse?
Wouldn't the reference (composite reference) use the host api to
register with the binding transport? I may not have worded things
clear enough. This way we separate the protocol binding and callback
mechanisms from the particular transport (e.g. Jetty)?
The binding would need to use the host API to register its inbound
transport and create an endpoint. This seems to be the same
function it would be doing on the Service side for traditional
inbound requests. Perhaps we should investigate merging the two
functions.
Yes.
3. We will need to have a conversational scope container and
persistence service
I take it those are independent services.
Yep. The persistence service I think can be a general thing for a lot
of other purposes as well.
4. I'd like to hook in Meeraj's work manager into this as well.
It's ready to go as soon as Geronimo publish the JSR237 API. I hope
they can get a SNAPSHOT out today; it if looks like it it taking
longer I may just copy it into our spec tree.
Great. Thanks Meeraj!
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
