-
-
Notifications
You must be signed in to change notification settings - Fork 751
Terminology
jfarcand edited this page May 28, 2012
·
2 revisions
The Atmosphere Framework contains several modules, which can be used depending on your needs. All modules are supporting Websockets and Comet Technique. To decide which module is the most appropriate, take a look at this blog
- Atmosphere Runtime: This module can be used to write POJO written in Java, Scala, JRuby or Groovy. The main components are AtmosphereHandler, WebSocketHandler and Meteor. An AtmosphereHandler can be used to suspend, resume and broadcast. A Meteor can be used with existing Servlet or Servlet based technology like JSP, JSF, Struts, etc.
- Atmosphere Jersey: This module can be used to write REST & Asynchronous Web application. The REST engine used is Jersey.
- Atmosphere GWT: Atmosphere extension for the GWT framework.
- Suspend: The action of suspending consist of telling the underlying Web Server to not commit the response, e.g. to not send back to the browser the final bytes the browser is waiting for before considering the request completed.
- Resume: The action of resuming consist of completing the response, e.g. committing the response by sending back to the browser the final bytes the browser is waiting for before considering the request completed.
- Broadcast: The action of broadcasting consists of producing a message and distributing that message to one or many suspended responses. The suspended response can then decide to discard the event or send it back to the browser.
- Understanding Atmosphere
- Understanding @ManagedService
- Using javax.inject.Inject and javax.inject.PostConstruct annotation
- Understanding Atmosphere's Annotation
- Understanding AtmosphereResource
- Understanding AtmosphereHandler
- Understanding WebSocketHandler
- Understanding Broadcaster
- Understanding BroadcasterCache
- Understanding Meteor
- Understanding BroadcastFilter
- Understanding Atmosphere's Events Listeners
- Understanding AtmosphereInterceptor
- Configuring Atmosphere for Performance
- Understanding JavaScript functions
- Understanding AtmosphereResourceSession
- Improving Performance by using the PoolableBroadcasterFactory
- Using Atmosphere Jersey API
- Using Meteor API
- Using AtmosphereHandler API
- Using Socket.IO
- Using GWT
- Writing HTML5 Server-Sent Events
- Using STOMP protocol
- Streaming WebSocket messages
- Configuring Atmosphere's Classes Creation and Injection
- Using AtmosphereInterceptor to customize Atmosphere Framework
- Writing WebSocket sub protocol
- Configuring Atmosphere for the Cloud
- Injecting Atmosphere's Components in Jersey
- Sharing connection between Browser's windows and tabs
- Understanding AtmosphereResourceSession
- Manage installed services
- Server Side: javadoc API
- Server Side: atmosphere.xml and web.xml configuration
- Client Side: atmosphere.js API