Hi!
Andy \"Mad\" Schaefer wrote:
> > The drawback of this solution is that the client and server has to be on
> > the same subnet (because Jini uses multicast for lookup). This will not
> > be a big problem in most cases since the most common case is to use a
> > webserver as client, which almost always is on the same subnet. If
> > anyone objects to this assessment, please let me know and I will take
> > into account clients on different subnets (Jini can work in this case
> > too, but not as dynamic).
>
> The problem for JMX Connector is that you do not know from where the
> administrator is located and therefore this can lead to a problem because
> the JMX administrator should be able to lookup the different jBoss
> instances.
>
> Do you have an idea if this is a problem for the JMX Connector (client
> side)?
It will take some additional thinking, but is not a big problem. The JMX
connectors will have to be bound into node-specific names that's all.
I.e. the JMX client will perhaps have to look up all names in a given
subcontext, all of which point to different servers.
Or something like that.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
