This doesn't have to be a different listener class. Since the TC cluster events listeners are expressed as interfaces, the same class can implement DsoClusterListener and MyAppFlummybopListener as is traditionally done in Java. I totally agree that we should allow developers to easily trigger custom events *on the cluster*, that is however imho different from events that come *from the cluster itself*. Hence I would create a TIM for this with possibility solutions to eventing on the cluster and not include this in the core.
On 28 Jan 2009, at 09:46, Sergio Bossa wrote: > On Wed, Jan 28, 2009 at 1:36 AM, Taylor Gautier > <tgaut...@terracottatech.com> wrote: > >> However, I think Sergio's point should be considered here. He is >> basically >> saying that you have to write a listener for a node death event, >> and a >> different listener for the custom user event. >> If I understand his request right, it would be a unified approach for >> applications to send events, combined with the tc level events so >> that there >> is not the added complexity of different listeners for what amounts >> to the >> same thing - process inbound events. > > Absolutely correct! -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Flytecase Band - http://flytecase.be Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
