-
-
Notifications
You must be signed in to change notification settings - Fork 751
WebSocket default protocol configuration
jfarcand edited this page Jun 27, 2012
·
2 revisions
If you are planning to use WebSocket with Atmosphere, make sure you understand the following fact: when a Websocket message is received, the message is translated, by default, to a fake HTTP request. By default, the method is a POST and the content-type is set to text/plain. You can change the default by adding, in your web/application.xml:
<init-param>
<param-name>org.atmosphere.websocket.messageContentType</param-name>
<param-value>..content-type...</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.websocket.messageMethod</param-name>
<param-value>...METHOD...</param-value>
</init-param>
You can also configure the maximum of time a connection can stay idle by adding, in web/application.xml
<init-param>
<param-name>org.atmosphere.websocket.maxIdleTime</param-name>
<param-value>{ default is 5 minutes } </param-value>
</init-param>
You can also configure the maximum size of message sent:
<init-param>
<param-name>org.atmosphere.websocket.maxTextMessageSize</param-name>
<param-value>{ default is 8192 } </param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.websocket.maxBinaryMessageSize</param-name>
<param-value>{ default is 8192 } </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