#websocket #api #programming

= = =

The topic of this video is WebSocket. Traditional computer communication methods, such as HTTP, involve the client sending a request and the server responding, creating one-way communication. This model has limitations, especially in real-time applications like chat apps, where the server cannot notify the client of new messages without a client request.

Polling and long polling are methods to address this, but they have drawbacks like delays and increased server load. WebSocket, however, allows bidirectional communication, similar to a phone call, enabling both the client and server to send messages freely and efficiently.

WebSocket starts with an HTTP handshake, then switches to the WebSocket protocol for ongoing communication, reducing overhead compared to HTTP. It is more resource-efficient and suitable for real-time updates, unlike HTTP/2, which is not designed for long-term bidirectional communication. WebSocket uses TCP, ensuring data order and reliability, making it ideal for applications needing real-time communication, like online games and stock apps.

However, WebSocket implementation can be complex, especially with load balancing, and message size limitations can be a concern. Security is also a consideration, requiring SSL/TLS for encryption. While WebSocket is less burdensome than polling, it still demands resources, and high user numbers can strain servers.

The video concludes by hinting at exploring alternatives to WebSocket in future videos.

свернуть