2 ms·
Why did HTTP/2 impact Websocket's usage? Websockets are still used for real-time server-client communication in many application stacks.
by chrisco255 8y ago
Why did HTTP/2 impact Websocket's usage? Websockets are still used for real-time server-client communication in many application stacks.
- derefr 8y agoIf your use-case for Websockets was "make a bunch of concurrent RPC requests without the browser queuing them" then you can achieve the same concurrency semantics using regular AJAX REST calls, as long as they happen to transit over HTTP/2. For a lot of people, that was all they wanted. As well, if you add a single SSE channel to that, riding in the same HTTP/2 socket, you now can do everything Websockets can do. And if you throw a web server like Caddy between your HTTP/2 clients and your application server, now your app server can just be implemented in terms of regular HTTP/1 request-handling, with no need to implement any connection-oriented protocols at all.
- Can_Not 8y agoCan you clarify what mainstream backend frameworks support any of those?