They're complimentary. ResettableEventBus is still hard to use from inside a widget because you're already have an interface to register.
So the pool concept is when you already have HandlerRegistration objects. However, this new WidgetLoading delegate does make it easier. On Mon, Sep 13, 2010 at 4:28 AM, Thomas Broyer <[email protected]> wrote: > > > On Sep 13, 1:15 am, Jarrod Carlson <[email protected]> wrote: >> Well, when I say "always present", I mean _probably_ always present. So in >> this case, simply not unregistering _shouldn't_ be an issue. Your use of a >> HandlerRegistrationPool is clever... I might try that; thanks. > > Well, if I were you, given your description of the use case, I'd use a > ResettableEventBus (StopperedEventBus in 2.1.0.M3). > If you don't want to unregister all your handlers in onUnload, then > mix EventBus and ResettableEventBus, or even use several > ResettableEventBus. > In other words, ResettableEventBus is very similar to Patrick's > HandlerRegistrationPool, just specialized in handling registrations on > an EventBus rather than HandlerRegistrations from any kind of registry > (EventBus or HandlerManager, which are distinct things post-M3). > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
