Développement d'applications WebSocket
WebSocket 1.1 is enabled by default and builds on the 1.0 specification. WebSphere Application Server Traditional uses the WebSocket protocol to enable applications to communicate by using a full-duplex connection.
Pourquoi et quand exécuter cette tâche
You can use WebSocket endpoints to match an endpoint to a URI. Web applications can use URIs that match a WebSocket template, but do not map to WebSocket endpoints. The distinction between mapping a WebSocket endpoint to a URI, or allowing the URI to be treated as a non-WebSocket HTTP Request, is made by the presence or absence of an Upgrade header with a value of websocket in the request.
In addition to the WebSocket version 1.1 API that is defined in the specification, JSR 356, an API was added to the WebSphere Application Server implementation to allow a servlet or filter to request that the current HTTP request upgrade to start a WebSocket session. For more information about the additional API, see API Specifications.
Outbound WebSocket API calls are available in applications running on the server, but not in WebSphere Application Server client applications. For more information, see Types of client applications.
Pour obtenir des informations sur le développement d'applications WebSocket à l'aide des outils de développement WebSphere, voir Développement d'applications WebSocket.