On Mon, Jan 19, 2009 at 4:58 PM, Geert Bevin <[email protected]> wrote:
> The cluster events we're thinking of in the light of this redesign is to > provide information about the state of the cluster that is not possible to > obtain otherwise. Extending this towards allowing people to register and > trigger their own events through the server would imho cross the lines of > the purpose of Terracotta. DSO gives you the core tools to make things > possible, not necessarily with a ready-cooked implementation or interface > for all use cases. We extend that functionality through TIMs that are much > higher level. So the way I see it is that as long as the cluster events > redesign allows a TIM to be written with higher level features, its scope is > correct. Absolutely agree: if the new TC events API will allow developers to extend them in order to support custom events, that will be the perfect solution. > I suggest that I write out the detailed spec and API proposal first. If you > have time, it would be awesome if you could check that the low-level > features you needed for master/worker are now there to at least make it > possible to implement your needs. Sure: let me know as soon as your proposal draft will be ready. > We can then later see about maybe creating > a TIM with a higher level scope. Then please consider me as a volunteer for such a TIM ;) 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 [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
