A short conversational clip (two speakers) discussing whether HTTP or WebSockets is the better transport protocol for signaling in web applications. Speaker B advises that if starting from scratch one might start with HTTP but will likely rely on WebSockets (or similar) to push information from the server to clients as needs grow.
Which is better as a transport protocol for signaling HTTP or WebSockets.
That depends on what your existing application if you have one uses the way or the reason for choosing one is typically that your existing chat application if you have one uses either WebSockets or HTTP or maybe Socket IO is an abstraction over that and that is basically the transport protocol, the underlying one for web PC signaling.
Okay, but let's say I'm starting something from scratch, I'm building my own application never existed before. Which one would you choose for that? For such an.
Application you might start with HTTP and that's what you would do unless you know that you're going to exchange more information with the server on the backend. The answer to that is almost always you will be using WebSockets to push information to the client.
So even if I'm going to want to try with HTTP I'll end up using websockets in the end or something similar.
Yes.
Meta rebuilt AV1 for mobile scale. Should smaller teams follow? | Chats with Arin
