3 ms·
"It's safe to assume that anyone who hopes to leverage websockets will not be using a blocking application architecture." No, it isn't. I'll wager that right
by timr 13y ago
"It's safe to assume that anyone who hopes to leverage websockets will not be using a blocking application architecture."
No, it isn't. I'll wager that right this very second, there's someone out there incorporating websockets into their Heroku-based Rails app and not thinking about (or understanding) the consequences.
- wmf 13y agoWouldn't such an app be hosed on almost any platform due to massive memory waste?
- gnur 13y agoI don't think the memory waste is the problem in this case, a websocket is a long lived connection. If you mix it with regular requests and don't think about the concurrency consequences you'll be able to serve 1 request and then allow for 1 websocket connection and your done. All other connections will be pending until the websocket is closed.