-
-
Notifications
You must be signed in to change notification settings - Fork 751
Recovering AtmosphereResource State between reconnection
Sebastian Lövdahl edited this page Jun 26, 2013
·
3 revisions
AtmosphereResourceStateRecovery is only available in version 1.1.0 and later.
When a connection get closed by a proxy, the client or the server, an AtmosphereResource state will be destroyed, e.g. the resource will be removed from all Broadcaster the resource was added. If your application needs to recover from a disconnection it's previous state, install the AtmosphereResourceStateRecovery interceptor by adding it to your annotation
@ManagedService(path = "/", interceptors = AtmosphereResourceStateRecovery.class)
public class myResource {
}
or by defining it in web/application.xml
<init-param>
<param-name>org.atmosphere.cpr.AtmosphereInterceptor</param-name>
<param-value>org.atmosphere.interceptor.AtmosphereResourceStateRecovery</param-value>
</init-param>
// application.xml
<applicationConfig>
<param-name>org.atmosphere.cpr.AtmosphereInterceptor</param-name>
<param-value>org.atmosphere.interceptor.AtmosphereResourceStateRecovery</param-value>
</applicationConfig>
By default, the state will be stored for 1 minute. You can change that value by adding
<init-param>
<param-name>org.atmosphere.interceptor.AtmosphereResourceStateRecovery.timeout</param-name>
<param-value>value</param-value>
</init-param>
- 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