I don't really see this as an issue remoting should address any differently.  
The reason is that I see this as the responsibility of the client registering 
the callback server.   If the server is not going to be able to call back 
directly to the client's callback server, they should use pull callbacks.  

If the client does register a callback server that the target server can not 
call back on, it will throw the exception back to the handler.  I think it is 
important for the invocation handler to know that the callback did not succeed 
in this case.  

However, would probably be good to provide an easier way for the invocation 
handler to remove the callback handler from the ServerInvoker (can currently do 
this, but takes some effort).

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865716#3865716

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865716


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to