[jboss-dev-forums] [JBoss AS Development] - Re: Naming over Remoting 3

[ron.sigal@jboss.com]

"david.lloyd at jboss.com" wrote : 
  | Also, please realize that if you've gotten something out of JNDI over the naming service, you should already have a connection to the server (or as Brian points out, at least one of the cluster). Or the server may have a connection to you. Getting or creating the proxy should not necessarily cause the creation of a connection, in my opinion. We need to figure out a way to decouple the creation of connections from the service (they even have separate URI schemes), otherwise the whole idea of multiple clients sharing a connection is defeated.
  | 

In Remoting 2, there is a level of indirection between user facing Client objects and network facing invokers.  If an app creates two Clients with the same InvokerLocators and the same config maps, they will share the same invoker, which, depending on the transport, typically means sharing the same connection pool.  In other words, creating a Client does not necessarily imply creating a new connection.

What about doing the same thing in R3 Endpoint.connect()?  I.e., keep a repository of reusable connections, keyed on URI and OptionMap?

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

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