Skip to content
pierreh edited this page Mar 19, 2013 · 19 revisions

There a are three main modules you can choose from:

  • proprietary GWT modules atmosphere-gwt-client/server These modules need to be used together and have their own transport mechanism and a GWT handler on the serverside. It has no other client dependencies, fully written in GWT, but does not integrate with Jersey. (Deprecated, in maintenance mode) See Using GWT

  • Wrapper around atmosphere-jquery atmosphere-gwt-wrapper This module is a thin wrapper around the atmosphere-jquery client and adds JSON and GWT-RPC object serialization on top. On the serverside an injector is used to handle the GWT-RPC serialization, this means it integrates well with existing Atmosphere Handlers. When using plain JSON on top of Jersey an interceptor is not even needed. (Preferred)

  • Polling GWT-RPC atmosphere-gwt-poll Single independent module to enable long-polling support on top of standard GWT-RPC AsynServices. Allows you to decouple the thread, do background processing in another thread and return the result when done.

GWT Support Modules

An overview of the modules:

  • atmospere-gwt-common Is a modules that contains some constants and interfaces shared among a few modules

  • atmospere-gwt-extra This module contains some high level features not needed for basic implementations. Like AtmosphereProxy which enables inter-window communication

  • atmosphere-gwt-jackson Support module to provide serverside JSON serialization. Integrates with atmosphere-gwt-server and atmosphere-gwt-wrapper

  • atmosphere-gwt-js Javascript export around the propriety atmosphere-gwt-client. Allows you to use plain javascript on top of the GWT module.

Clone this wiki locally