GWTEventService - Release-Notes

GWTEventService - Release Notes

Features / Advantages

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

GWTEventService 1.2.1

The maximum amount of events which is processed at once (within one call/request) can now be configured/limited and is set to 1.000 by default. Property: "eventservice.events.max"
Configuration dependent factories optimized and introduced lazy-loading
Various optimizations and fixes for the configuration loading mechanizm
Various code optimizations
Issue33: The waiting user threads were not terminated directly when the user were removed by an unlisten call.
Issue42: Client-side concurrency problem fixed which could occur when a listener gets added while received events are concurrently processed.
Issue49: The daemon thread to detect user/client timeouts is now stopped automatically when the EventService-Servlet gets deregistered.
Issue52: The waiting user threads were not terminated directly on server shutdown (when the JVM were not terminated).
Issue55: Concurrency problem fixed which could occur when GWTEventService is deployed on GlassFish.
(Tests revised with JUnit 4 and Mockito)

GWTEventService 1.2

Support for multiple / shared sessions
Support for streaming added (alternative to long-polling)
Support for individual service mappings (for example required for GWT-RPC-Spring)
Support for automatic reconnect added (automatic client side reconnect when the connection is lost)
Support for optional configuration parameters added
Support for various connection strategies added (server and client side)
Possibility to add events directly from the client side
Introduction of a user-specific domain (explicit domain additional to the implicit NULL-domain)
Intoduction of the ClientHandler to transfer the connection-/client-id to custom server-side services
Configuration access possibilities at the client side implemented (the server side defined configurations can now be accessed at the client side)
Client side timeout listener extension realized (when the request to the server fails the callback and the UnlistenListener get informed)
Introduction of Maven as the new build system and new project stucture (Maven conventions)
Logging improvements
Some code and structure refactorings
Bugfix: One possible concurrency issue fixed (rare problem)
Issue17: UserActivityScheduler is now a daemon thread. That makes sense and solves a freeze issue with Tomcat on Ubuntu (9.10).
Issue19: Support for Automatic reconnect (see above)
Issue24: An unlisten call for the NULL-domain caused a deactivation (complete unlisten) even if the user is still registered for another domain.
Issue26: Support for individual service mapping added (see above)
Issue27: Exception solved which occurred when all listeners were removed, a session-timeout occurred and after that a new listener was registered.
Issue30: Blocked request without GWT permutation header (rare problem)
Issue32: Status code 0 which is sent from some browsers will now be handled correctly.

GWTEventService 1.1.1

Issue14: Compatibility for JDK 1.5 / 5.0 ensured
The end of service life of JDK 1.5 / 5.0 was actually reached on 2009-11-03 (see http://java.sun.com/javase/downloads/index_jdk5.jsp), but some productive environments may not be migrated to JDK 1.6 / 6.0 at the time. The compatibility for JDK 1.5 / 5.0 should therefore be ensured.
Issue16: Support for full-qualified configuration parameters added for the web descriptor configuration.
Small performance optimizations
System requirements introduced (system requirements)

GWTEventService 1.1

Support for unlisten and timeout listening (new UnlistenEventListener) added
Support for web deployment descriptor configurations added
EventFilter enhancements
Support for GWT 2.0 added (for the demo projects, the core is compatible with GWT 2.0 since version 1.0)
Revised configuration loading
Concurrency optimizations
Multi-threading improvements
Platform refactoring
Logging improvements
New demo application "HelloGWTEventService"

GWTEventService 1.0.2

Issue6: The callback wasn't used when a listener is removed without a domain (domain-less listener)
Issue7: Empty domains weren't removed automatically
Issue8: Possible dead-lock when a user is registered and another user is concurrent deregistered
Improvements for domain-less usage
Concurrency optimizations

GWTEventService 1.0.1

Bugfix: Work-around to avoid multiple session creation (GWT issue 1826) when GWTEventService had to execute the first server call of the application
Bugfix: Client side multi-threading bug fixed, which could occur when a listener is removed while processing listen results
Issue3: Chrome appeared as if the page never finishes loading when GWTEventService had to execute the first server call of the application
Client commands introduced to solve the problems described above (new interfaces ClientCommand and ClientCommandScheduler)
Some client side optimizations

GWTEventService 1.0 (Changes from 0.9 to 1.0)

Logging improved
Bug fixes
Some small improvements
No API changes compared to GWTEventService 0.9
Documentation completed
Build scripts updated

Project home (online)