-
-
Notifications
You must be signed in to change notification settings - Fork 751
Frequently Asked Questions
Jeanfrancois Arcand edited this page Feb 13, 2015
·
86 revisions
- Enabling Native Support
- Configuring Atmosphere as a Spring bean
- Configuring Atmosphere
- Forcing jsr356 WebSocket Support
- Keeping Track of AtmosphereResource between reconnection using an AtmosphereSession
- Migrating from 1.0.x to 2.0.x
- Downloading SNAPSHOT builds
- Using Atmosphere Runtime's annotations
- How to discover supported transports between browsers and server
- Multiple messages arrives as single response body or messages are incomplete
- Configuring WebSocket default protocol
- Detecting Browsers closing a connection
- ClassNotFoundException at Startup
- Enabling HttpSession support
- Sending Binary Data using WebSocket
- Retrieving the original AtmosphereResource with WebSocket
- HOW TO execute : Server Side Broadcasts OR Communication from Server Sides OR Non HTTP initiated Broadcast
- NullPointerException/IllegalStateException on Broadcast
- Using the beforeUnload Javascript function
- Built-in WebSocket Protocol and how to use it
- Enabling native asynchronous support for WebLogic 11 and lower
- Keeping a connection active using a Heartbeat AtmosphereInterceptor
- Enabling CORS
- Using Atmosphere with other frameworks like RestEasy, Wink or Struts
- Streaming WebSocket's text or binary
- AtmosphereHandler not being found when using NetBeans IDE
- Creating private channel of communication between browsers
- Configuring the maximum number of threads used by a Broadcaster
- How to run Atmosphere behind Apache WebServer
- Installing WebSocket support for JBoss 7.1.2 and up
- Timing out idle WebSocket connections
- Timing out Broadcaster's write operation
- What does this means? The WebSocket handshake succeeded
- AtmosphereHandlerService: No AtmosphereHandler found. Make sure you define it inside
- Using BroadcasterCache with TrackMessageSizeFilter
- Forcing Atmosphere AsyncSupport
- Deploying Atmosphere Jersey in JBoss
- Detecting situations when the browser closes the connection when using long-polling
- [Debug message: Invoking BroadcastFilter with dummy AtmosphereResource] (https://github.com/Atmosphere/atmosphere/wiki/Debug-message:-Invoking-BroadcastFilter-with-dummy-AtmosphereResource)
- Forcing Servlet 3.0 and WebSocket AsyncSupport
- Blocking browsers that use old WebSocket specification
- Recovering AtmosphereResource state between reconnections
- Configuring Nginx for WebSocket and long-polling
- Configuring the TrackMessageSizeInterceptor
- Adding SSE support to Internet Explorer and old browsers
- Using URI path templates with annotated classes
- How to specify Spring Servlet with Atmosphere
- Auto-detection of Atmosphere handlers fails in specific deployments
- JMS, XMPP, ... (via AbstractBroadcasterProxy) : Broadcast to a specific resource
- Using the latest Javascript Client with Atmosphere 1.0.15 and up
- @Singleton -> ClassCastException on broadcaster.addAtmosphereResource() w/ Jersey resource
- Using Akka
- Using Guice, Spring, CDI or any Injection Framework
- WebLogic 12.1.2 WebSocket Support
- java.io.IOException: Message Buffer too small
- Surviving proxies that strip WebSocket's Request Header
- Atmosphere shutdown hook: Executing tasks during undeploy
- How to use the older WebSocket draft-00/hybi-00/hixie-76 protocol
- Atmosphere startup hook: Executing task after deploy
- Atmosphere and Apache/Tomcat AJP Protocol
- Enabling WebSocket support in JBoss EAP 6.3 and up
- Using Spring Request Scoped Beans in Atmosphere Requests
- java.lang.IllegalStateException: JBoss[Tomcat] failed to detect...
- Clustering Atmosphere using Apache TomEE and ActiveMQ
- Getting BroadcasterFactory and AtmosphereResourceFactory with 2.2 and newer
- Using Apache Shiro
- [Apache and Tomcat default ports issue with Trend Micro agent] (https://github.com/Atmosphere/atmosphere/wiki/Apache-and-Tomcat-default-ports-with-websocket-transport)
- [No AtmosphereHandler found when using hierarchical classloaders] (https://github.com/Atmosphere/atmosphere/wiki/No-AtmosphereHandler-found-when-using-hierarchical-classloaders)
- Running Atmosphere with Apache Kafka
- 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