> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Bordet, Simone
> Sent: Wednesday, September 12, 2001 9:24 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-dev] JINI - JavaGroups - Whatever: real issue?
>
>
> Hi,
>
> > A client (whether an application or server) should be able to
> > auto-discover
> > the EJB proxy object anywhere in the network. This seems to be Jini's
> > strength. Regardless of the discovery process, if I am making
> > a call on this
> > proxy and the server is no longer available, the *proxy*
> > should reconnect to
> > another server in the cluster. This should be this
> > transparent to the user.
>
> This is possible also in Jini, via the LookupCache.
> The trick is the transparency for the client that should only do new
> InitialContext().lookup("foo") and obtain the fail over proxy for the EJB.
> I'm working on this part for a project (that unfortunately doesn't involve
> JBoss, but is very similar to it, albeit waaay simpler), and it
> seems to me
> there are 2 ways, using Jini:
> - rewrite JNDI on top of Jini
> - use Rickard's smartworld proxies (and I'm not sure if this will require
> the former bullet, still investigating)
>
> Don't know JG, but how do you (Bill, Sacha) plan to share the server state
> among nodes ? Remote events ? JG specific stuff ?
>
We've written a small framework around JG. As I've said before, JG provides
RPCs, change of membership events, and a state transfer protocol that the
framework plugs into.
Jini will not be considered for our first iteration. But will be considered
for later iterations.
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
