Remote event listening for GWT

Some nasty thing with GWT was, that if you wanted your client to get notified about changes on the server, you had to use polling. Like a Timer that makes  a RPC every 500ms. That isnt very handy or elegant not just because it causes a lot of traffic but also because its long-winded. More clever would be some kind of Events and the corresponding Listeners.

To get rid of that you can use GWTEventService.

GWTEventService is an event-based client-server communication framework. It uses GWT-RPC and the Comet / server-push technique. The client side offers a high-level API with opportunities to register listeners to the server like to a GUI component. Events can be added to a domain on the server side and the listeners on the client side get informed about the incoming events. The server side is completely independent of the client implementation and is highly configurable. Domains can be defined to decide which events are important for the different contexts.

Advantages

• Encapsulation of the client-server communication
• High-level API with listeners and events
• Only one open connection for event listening
• Reduction of server calls
• Reduction of connection peaks
• Events are returned directly when the event has occurred (instead of polling)
• Events are bundled to reduce server calls
• Based on the GWT-RPC mechanism
• Automatic timeout recognition and handling
• Extensible architecture

Advertisement