-
-
Notifications
You must be signed in to change notification settings - Fork 750
Keeping Track of AtmosphereResource between reconnection using an AtmosphereSession
Starting with Atmosphere 2.1, The AtmosphereSession class can be used when an application needs to retrieve the AtmosphereResource associated with a remote client's unique UUID. An AtmosphereResource is created when a connection is made to the server, and this object will stay valid until the connection is closed. If the connection gets closed, the AtmosphereResource will becomes invalid, hence an application refering this object will no longer be able to use it. Instead, it is recommended to use an AtmosphereSession and call the appropriate method to retrieve the AtmosphereResource. For example: as soon as the AtmosphereResource gets created, you create the AtmosphereSession
AtmosphereSession session = new AtmosphereSession(anAtmosphereResource);
// Store the session somewhere
Later, retrieve the same of newest AtmosphereResource representing the remote client
AtmosphereResource r = session.tryAcquire();
By default, the calling Thread will wait 30 seconds and then returns null
in case the client hasn't connected. You can configure the timeout:
AtmosphereResource r = session.tryAcquire(5); // Wait 5 seconds, and return null in case no reconnect.
- 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