3 ms·
I don't understand the benefit ??? This seems like unnecessary overhead for any startup software companies, costing both extra time and money while overloading
by snejad123 6y ago
I don't understand the benefit ???
This seems like unnecessary overhead for any startup software companies, costing both extra time and money while overloading your server right out the gates.
Instead of expecting 100 requests per min from say like 20 users, I can now expect 1000s+ to my server because I'm sending every keystroke to the server ???
That means I'll need a super expensive instance to handle all those users and this is in the extremely conservative use-case of 20 users at once.
No thanks.
- dynamite-ready 6y agoNot quite. With requests over HTTP, there's an overhead for every single request. For websockets, you make one fat handshake/upgrade request to start with, and then all successive "requests" (frames) have no headers. So depending on what you're doing, and how you do it, it can be more efficient.
- MaxBarraclough 6y ago> With requests over HTTP, there's an overhead for every single request. Doesn't this go away with HTTP/3 and wherever QUIC is used?