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 less clear about how they fit in except for some very niche uses. If this becomes a core Rack specification and now forces all Rack implementation to carry around websocket framing protocol and epoll/kqueue I would also be less excited. On Sat, Aug 6, 2016 at 5:37 PM, Boaz Segev <[email protected]> wrote: >>> Michael said >> Unicorn is a forking webserver, not an event-driven or threaded >> webserver. Whether Unicorn ever supports the proposed standard or >> not, I wouldn't recommend it be used for typical applications that use >> WebSockets, as they usually involve persistent connections. Unicorn >> would quickly run out of worker processes capable of serving such >> connections anyway, so I question whether it's worth delving into the >> dirty details of IO syscalls. > > >>> Eric said >> Sorry, not interested, and definitely not touching centralized >> message boards :> > > > I totally understand and I thank you both for your time. > > -- Bo. >
