Andreas Schaefer wrote:
> Forgive me when I am wrong but JINI and JMX have some similarities
> but mostly they are quite different.
Exactly.
> JINI allows to create a dynamic community where services can appear
> or disappear and the services get notified dynamically. You can also
> search for a service w/o knowing the implementation like you want a
> color printer but you don't care which one.
>
> JMX allows you either to offer a management interface or to use the
> offered management interface to manage the components. BUT JMX
> works locally and have no notion of a network. You can add an Adaptor
> and/or Connector to manage remotely but there is not further description
> on the spec. (and most people mix up the Adaptor and Connector as well).
> One similarity is that you can search for a component according to its
> properties, of course, only when the properties are set well.
Yup, that's it.
> JINI would allows JBoss to create a dynamic community of J2EE servers
> and JMX would allow us to manage the components.
Precisely.
> This leads me back to my proposal of generating a collective of servers
> (yeah, your right, the BORG collective, because each server should know
> the whole configuration allowing the collective to work even when a
> member dies or is temporary unavailable IN CONTRAST to the
> community of specialized servers like Master/Slave model) where JINI
> build up the collective and JMX is the communication channel.
Which is very similar to what I proposed I guess it was a year ago when
I started rambling about Jini for clustering. I'm all with Andy on this
one.
/Rickard
--
Rickard �berg
Software Development Specialist
xlurc - Xpedio Link�ping Ubiquitous Research Center
Author of "Mastering RMI"
Email: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
