+1 On Tue, Sep 29, 2009 at 2:37 PM, Chris <[email protected]>wrote:
> > Just had a quick question... I can see the benefits of the > CommandPattern to some extent, what I'm not sure about is why, if > we're using an Event Bus on the client side, one might not try and use > an event bus on the server side too with an "event bridge" (you might > say) in the middle. > > - Each event would define whether it propagates to the server. > - The clients would be listening for events and all they would see is > their relevant events being fired. They wouldn't know whether the > event originated from the server and the client. > - The server components would be listening on to the server-side event > bus. In this case, the server would just fire off its response in the > form of an event that all other server components could see and if > need be this would propagate to the clients. > > Just wondering what people think of that pattern? I'm rather new to > GWT and want to make my app as simple as possible, and it seems to me > it would be rather nice if my > > Client Module says: "I need a list of names", > Server Module sees message "someone needs a list of names". > Server Module says "Someone needed a list of names and here it is"... > > I guess in that way, the response can be shared by many clients. The > bridge in the middle could do some caching/filtering in the middle, > since clearly not all events would need to be propagated to the > server... > > Just some thoughts... > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
