WebSocket

Description

Whether to deploy a real-time service as a WebSocket service. By default, APIs of real-time services are accessed using HTTPS. If you select WebSocket during real-time service deployment, the API URL is a WebSocket address after the service is deployed.

This function is supported only if the model is WebSocket-compliant and comes from a container image.
This function cannot be enabled together with Traffic Limit.
This parameter cannot be changed after the deployment.

FAQs

What Are the Differences Between WebSocket Access and HTTP/HTTPS Access?

WebSocket is a network transmission protocol that supports full-duplex communication over a single TCP connection. It is located at the application layer in an OSI model. WebSocket simplifies data exchange between the client and the server and allows the server to proactively push data to the client. In the WebSocket API, if the initial handshake between the client and the server is successful, a persistent connection will be established between them and data can be transferred bidirectionally. This is suitable for real-time communication and bidirectional communication.

HTTP is an application-layer protocol based on TCP. It consists of requests and responses and is a stateless protocol. Each request or response is independent. It applies to the transmission of static content and requests, but not to the real-time communication.

HTTPS is a secure version of HTTP and uses SSL or TLS to encrypt data. It is a transmission protocol for secure communication over a computer network.