On 12/08/14 22:41, Dan Berindei wrote: > > I like the idea of shipping the cache configuration to all the nodes. > We will have to require any user-provided objects in the configuration > to be serializable/externalizable, but I don't see a big problem with > that. > > In fact, it would also allow us to send the entire configuration to > the coordinator on join, so we could verify that the configuration on > all nodes is compatible (not exactly the same, since things like > capacityFactor can be different). And it would remove the need for the > CacheJoinInfo class... Can't we store the configuration defs in the cluster registry ? If a node attempts to overwrite an existing configuration based on the same name, an exception can be thrown.
Tristan _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
