Re: One v.s N EventBus

I am using one event bus across the whole app.

The definition of eventbus implies that, but who knows, I've never though about having multiple eventbuses.

Maybe you can find some benefit from doing that

2010/7/31 Sebastian Hoß <mail@shoss.de>

I've been using multiple EventBus instances together with Gin/Guice
and named annotations. So for example each view that needs to
communicate in some way with my REST server is attached to the @Server
HandlerManager. That way each component can have multiple
communication channels open and it is possible to re-use some events
across several buses. For example: I defined a simple FilterEvent
which takes a single String as an argument. Depending on the event bus
you are going to use you either filter on types or descriptions here
(so I don't need a FilterTypeEvent and FilterDescriptionEvent).

That said, I've moved away from multiple event buses since this can
get really confusing sometimes ...

On Sat, Jul 31, 2010 at 6:03 AM, Dean S. Jones <deansjones@gmail.com> wrote:
> Looking at finishing up an idea, and I have come across a thought in
> MVP: Global v.s a multiple/hierarchy of view/presenter EventBus's, and
> wondered if anyone
> had explored this avenue. The basics are there is the global EventBus,
> as is typical now, and a local EventBus for actions in the current
> View/Presenter, there
> may be even more levels, say per sub-panel/component, and the choice
> to propagate the events between levels. My current... idiom for using
> this is the dispatch
> of... "DataModelChange" events, when I don't really know exactly WHO
> in the current hierarchy is "listening" ( the UI is composed
> dynamically, so I don't have total
> foreknowledge of the components interests ). Using GIN/Guice for
> injection, obviously, I have to subclass the view/presenter EventBus
> to keep it distinct from
> the global EventBus type. So, just wondering if anyone has jumped into
> this, and what ideas/patterns have fallen out of it for you.
>
> --
> You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
http://ajax-development.blogspot.com/

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.