Re: [infinispan-dev] Hot Rod - pt2

On 16 Dec 2009, at 14:04, Galder Zamarreno wrote: >> I expect this to be declarative (in XML). Then you just filter the JGroups view against the nodes you have in the list of HR servers to determine what to send back. >> > I was expecting to this in similar to way to how clustered EJBs do. When > you you deploy a clustered EJB, it sends a sync message around the > cluster indicating to the other servers that there's a new endpoint for > that clustered EJB and hence, they update a server side list of HATarget > which is what is send back to the clients in piggyback. > > I was thinking that when a HR server deploys, I could do a similar > thing. You could then use the existing JGroups view id and associate it > with the current HR server target list. > > This however assumes that the server side HR servers are actually joined > in a single cluster, which might not necessarily suit all situations. > Maybe Mircea's suggestion makes sense - a separate, internal Cache instance that uses REPL_ASYNC or something, to propagate a HR server list. -- Manik Surtani manik(a)jboss.org Lead, Infinispan Lead, JBoss Cache http://www.infinispan.org http://www.jbosscache.org _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev