Re: Please join the Rack Specification discussion for `env['upgrade.websocket']`

Hi Sam, I just wanted to point out that the specification was meant to be optional and this is why it includes the `env['upgrade.websocket?']` flag to indicate support. I don't think every server has to support Websockets - different server architectures favor different tasks and performance

Re: Please join the Rack Specification discussion for `env['upgrade.websocket']`

Sam Saffron wrote: > For the record Eric, > > We use unicorn at Discourse to serve concurrent long polls across 100s > of hosted forums using hijack with zero issues using > https://github.com/SamSaffron/message_bus Thanks. That's exactly the usage I had in mind when I

Re: Please join the Rack Specification discussion for `env['upgrade.websocket']`

For the record Eric, We use unicorn at Discourse to serve concurrent long polls across 100s of hosted forums using hijack with zero issues using https://github.com/SamSaffron/message_bus I am not particularly enthused WebSockets and have blogged about my reservations, in an HTTP/2 world I am