News for hackers. Stuff that matters.
Re:Heroku WebSockets Now in Public Beta by timr on Tuesday October 08, 2013 @07:23PM (#6518531)
"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.

Re:Heroku WebSockets Now in Public Beta by wmf on Tuesday October 08, 2013 @07:36PM (#6518573)
Wouldn't such an app be hosed on almost any platform due to massive memory waste?
Re:Heroku WebSockets Now in Public Beta by gnur on Wednesday October 09, 2013 @06:45AM (#6520445)
I 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.