On Fri, Jan 16, 2009 at 6:04 PM, Taylor Gautier <tgaut...@terracottatech.com> wrote:
> 4) Master/Worker > - needs to know when a node has joined the system to re-balance work > across all nodes (although this can easily be coded with wait/notify) > - needs to know when a node (and which node) has left the system to > re-balance work from that node across remaining nodes I'd like to add some thoughts about the Master/Worker use case... Having notification for when a node joins and leaves the cluster is not enough: what if the node joins, but the worker process is not started? Or if it starts both a worker and a master process? How we may know if the joining/leaving node is a master or worker? What I mean to say is that we need to know both when a node joins/leaves, and when something interesting happens in that node. That is, it would be great to be able to send and receive notifications of user defined events during node lifecycle, i.e.: sending a user defined event when a node leaves the cluster. What do you think? > We also decided to focus on a non JMX API for several reasons: > * artificially introduces a whole infrastructure that is not needed and that > is leaky > * makes it more difficult for the developer to integrate > * is not a compile-type API, which means less safety > > We're going to design a POJO API with compile-time safety that is based on > dependency injection. Absolutely agree. Let us know as your POJO APIs get shaped up, so that we can help with our feedback. Cheers, Sergio B. -- Sergio Bossa Software Passionate, Java Technologies Specialist and Open Source Enthusiast. Blog : http://sbtourist.blogspot.com Sourcesense - making sense of Open Source : http://www.sourcesense.com Pro-netics s.p.a. : http://www.pronetics.it _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
