[Jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - NAT issues

[<sco...@jb...>]

I talked to a jboss user who indicated he needed to create a custom invoker to deal with firewall routing issues because the remoting layer did not have the notion of allowing the client endpoint to specify the connection info as an override. The basic scenario is pulling down a transport endpoint/proxy across a nating firewall where the server has no idea of the topology the client is going to be using.

This is something we support in the uil2 jms transport using a client side property for the server address/name and port.

We need something similar in the remoting layer as well. In talking to the jxta people, they have support for even more totorous types of paths so maybe there is an abstraction there we can incorporate.


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

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