Borland uses a program called smartagent to act as a broadcast point on a
subnet. This agent asks as a discovery mechanism for both the client *and*
servers. When an agent needs to "hop" subnets, it is required that the agent
have a list of at least one other agent on the other subnet. They also
include a gateway to tunnel this protocol through the firewall on port 80.
Regardless of the approach you use to cluster servers, I am interested in
hearing the plans for client discovery of servers. In many ways, this is the
crux of the problem, as server to server communication is actually just
client to server communication at some point.
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.
Borland accomplishes this by making the "proxy" aware of the smartagent.
jim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jason
> Dillon
> Sent: Tuesday, September 11, 2001 5:01 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] JINI - JavaGroups - Whatever: real issue?
>
>
> > > > Not really, except Jini can use Unicast as well. Multicast
> is bonus, but
> > > > not required. I don't know about JG on this point.
> > >
> > > But unicast does not help with clustering, we want multicast.
> >
> > Well, you still get the leasing support, it's just that you need more
> > admin to get it going (pointing out all nodes, etc.). Using multicast is
> > more admin-free, but it's not much more than that.
>
> Administration is a huge problem/burden, whatever we can do to eliminate
> this the better. If that means requiring a multicast enabled host machine
> for advanced cluster support then so be it.
>
> The alternative would be to maintain a static configuration on
> each node in
> a cluster which maps out the other nodes... yikes. Lets not go there.
>
> --jason
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
