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

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

The issue is how is the connection handled when the connection endpoint that the client needs to use is not known on the server side. It may not even be meaningful to have a name for the clientConnectAddress. If there is a name, we need a multi-step approach to resolving it at the time the client is making the connection. We can either code a multi-step behavior, or introduce an interface to externalize the resolution:

{{{
import java.net.InetSocketAddress;

public interface EndpointResolver
{
   public InetSocketAddress resolve(String name, int port);
}

}}}

We could also have a resolver chain notion to tier prioritize and stack the resolution process.


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

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