4 ms·
https://stackoverflow.com/questions/26003756/is-there-a-limit-practical-or-otherwise-to-the-number-of-web-sockets-a-page-op/26013035#26013035 https://stackoverf
by coder543 5y ago
https://stackoverflow.com/questions/26003756/is-there-a-limit-practical-or-otherwise-to-the-number-of-web-sockets-a-page-op/26013035#26013035 https://stackoverflow.com/questions/26003756/is-there-a-limi...
It appears to be 30 per domain, not “hundreds”, at least as of the time this answer was written. I didn’t see anything more recent that contradicted this.
In practice, this is unlikely to be problematic unless you’re using multiple websockets per page, but the limit of 6 TCP connections is even less likely to be a problem if you’re using HTTP/2, since those will be shared across tabs, which isn’t the case for the dedicated connection used for each websocket.
- jcheng 5y agoIt’s 255 for Chrome and has been since 2015, 200 for Firefox since longer than that. https://chromium.googlesource.com/chromium/src/net/+/259a070267d5966ba5ce4bbeb0a9c17b854f8000 https://chromium.googlesource.com/chromium/src/net/+/259a070... Agree that it should be much less of a problem with HTTP/2 than HTTP/1.1.