Hello, Sure by nature http does not support events instantiated on by the server. But there are some workarounds. Try to google for http server push, or comet.
Best - Istvan On Wed, Sep 30, 2009 at 4:51 PM, Trevis <[email protected]> wrote: > > The enherent problem with having a server side bus that talks to a > client bus is that the server can't initiate the event. . (due to the > non-push nature of the web) but the second issue is that a client bus > services one client where as the server bus would need to service > many. Questions spud arise like can a server event fire to a specific > client or only to an individual client? > > In the application that I'm developing I have a polling thread in the > gwt client and an event broadcast system on he server to allow the > server to notify clients of notworthy activities. I don't use a bus > on the server to handle requests though I just use RPC and command > pattern. > > On Sep 29, 4:09 pm, PJ Gray <[email protected]> wrote: > > Yeah, I have thought the same thing as I was implementing > > MVP/CommandPattern. I have a few eventbus events that I handle with > > EventHandlers, but then I have the whole gwt rpc mechanism that uses my > own > > generic action classes. > > > > Combining the two might be a good move, however it might get tricky > crossing > > the great wall of javascript. I am no gwt expert, so I don't know how > > tight a coupling you can get from your server side stuff and GwtEvent > > (assuming you still want to use eventhandlers). > > > > I am sure its doable though. > > > > -pj > > > > On Tue, Sep 29, 2009 at 3: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... > > > -- Best Regards - István Szoboszlai [email protected] | +36 30 432 8533 | inepex.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 [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 -~----------~----~----~----~------~----~------~--~---
