https://stackoverflow.com/a/42465368/462608
Where might websockets still have a place? The big one is server->browser pushed binary data. HTTP/2 does allow server->browser pushed binary data, but it isn't exposed in browser JS. For applications like pushing audio and video frames, this is a reason to use websockets.
What does it mean when they say that that pushed binary data isn't exposed in browser JS? I request some example to help me understand this.
https://stackoverflow.com/a/47108355
And so HTTP2 push is really something between your browser and server, while Websockets really expose the APIs that can be used by both client (javascript, if its running on browser) and application code (running on server) for transferring real time data.
I request some examples to make me understand the meaning of HTTP2 push is really something between your browser and server and Websockets (socket.io) has API which can be used by clients.
What does all this mean?
from What is the meaning of - HTTP2 doesn't provide API used by the clients, while websockets do?
No comments:
Post a Comment