[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step

2005-03-29 Thread [EMAIL PROTECTED]
I don't think it's necessary to add a new callback server specific implementation. You have all the wiring in there, I would just tweak a little bit ServerInvoker.handleInternalInvocation() so it won't get upset when someone tries to register callbacks when no handlers are present. Other than th

[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step

2005-03-29 Thread [EMAIL PROTECTED]
Ahh. Ok. I misunderstood what you were saying originally. For the callback server, if it is not handling any direct invocations, only callbacks, the I agree that there is no need for a handler to be registered (conceptually). However, I don't make a distinction, in the implementation, between

[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step

2005-03-28 Thread [EMAIL PROTECTED]
anonymous wrote : Remoting is just a mechanism for making remote invocations (including callbacks). It has no concept of contextual processing. There has to be a ServerInvocationHandler on the server side to process invocation requests, including adding and removing of callback listeners. The S

[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step

2005-03-24 Thread [EMAIL PROTECTED]
I posted a document that describes how callbacks work (in detal) on the wiki. Go to http://www.jboss.org/wiki/Wiki.jsp?page=Remoting and look for the "How callbacks work." link. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871575#3871575 Reply to the post

[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step

2005-03-24 Thread [EMAIL PROTECTED]
Remoting is just a mechanism for making remote invocations (including callbacks). It has no concept of contextual processing. There has to be a ServerInvocationHandler on the server side to process invocation requests, including adding and removing of callback listeners. The ServerInvocation

[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step

2005-03-24 Thread [EMAIL PROTECTED]
The ServerInvoker doesn't use the ServerInvocationHandler instance to process callbacks. It uses CallbackContainer instances. It also doesn't use the ServerInvocationHandler instance to register callback listeners, either. Look at ServerInvoker.handlerInternalInvocation(). For ADDCLIENTLISTENER

[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step

2005-03-24 Thread [EMAIL PROTECTED]
No, I'm pretty sure you need a handler. That's the thing that actually handles the incoming request (or in this case, the incoming callback). Its in your handler that you will process the callback data. If you don't don't add a handler - who is going to get your callback data? Who actually w