MC is the first pass. We can easily make a static plugin too. What I will check in makes used of a DiscoveryAgent interface (thank you AMQ), so with a small amount of code, we could do a statically specified list of servers, or even do discovery via a "check in" server.
Matt Hogstrom wrote: > > On Nov 14, 2006, at 6:16 PM, Jeff Genender wrote: > >> >> Yep, multicast for discovery and TCPIP for session communication for >> replication. Have a look at gcache in the Geronimo sandbox. >> > Will there be other ways of configuring the cluster beyond multi-cast. > MC is not universally available in some shops. >> >> Thanks, >> >> Jeff >> >> >> >>> Cheers, >>> Paulo >>> >>> On 11/14/06, Jeff Genender <[EMAIL PROTECTED]> wrote: >>>> Hi Guys, >>>> >>>> I need to get OpenEJB3 ready for some clustering. Here is a plan... >>>> >>>> I am going to add a multicast agent to openejb so that the containers >>>> can "find each other". The containers will create a list of endpoints >>>> (other servers) and stuff the list in the ServerMetaData as a list of >>>> URLs. That list will go to the client for use in the proxy. Currently >>>> OEJB2 uses round robin, but I would like to port it up to OEJB3 with a >>>> plugable strategy, so we can use "random" for EJB connectivity to >>>> provide for load balancing, as well as round robin. >>>> >>>> I would like to know about preferences for insertion points for the >>>> multicast agent, deployment configuration (to turn it on and use it), >>>> etc. >>>> >>>> All comments are welcome. >>>> >>>> Thanks, >>>> >>>> Jeff >>>> >>> >>> >> > > Matt Hogstrom > [EMAIL PROTECTED] > > "Give a man a fish and he will eat for a day. > Teach a man to fish and he will sit in a boat all day." >
