Using Atmosphere Runtime Annotations

The Atmosphere Runtime module supports extensions that can be used to replace or extend the runtime. The annotation supported are:

• AtmosphereHandlerService : At least one class must be annotated with this annotation if you are using AtmosphereServlet. The class must implements the AtmosphereHandler interface. See this tutorial for more information.
• BroadcasterCacheService : If you are planning to support your own BroadcasterCache implementation, use this annotation to tell Atmosphere to use it.
• BroadcasterFilterService : If you want to add BroadcastFilter to your application, annotate them using this annotation.
• BroadcasterService : If you are planning to support your own Broadcaster implementation, use this annotation to tell Atmosphere to use it.
• MeteorService : At least on class must be annotated with this annotation if you are using Atmosphere as as MeteorServlet. This class will install Meteor automatically.
• WebSocketHandlerService : If you want to write pure WebSocket application.
• WebSocketProtocolService : If you want to write your own WebSocketProtocol support for Atmosphere.
• AtmosphereInterceptor : Install AtmosphereInterceptor
• AsyncSupportListenerService : You can install a global events listener using that annotation. Read this document for more information.
• WebSocketProcessorService : Replace the entire WebSocket handling/supports in Atmosphere.