This issue is a discussion, not a bug report. I'm opening the question for discussion because:
1. With [AnyCable](http://anycable.evilmartians.io) in mind and in with the new [Websocket Rack specification proposal](https://github.com/boazsegev/iodine/blob/master/SPEC-Websocket-Draft.md), separation of concerns might be beneficial (similar to the way the web server was extracted). 2. The [Websocket-Shootout benchmark](https://hashrocket.com/blog/posts/websocket-shootout) had some very troubling results. I emailed Jack about it and he pointed out that ActionCable was crashing as well as slow. I believe that similar to the way the HTTP server was extracted from earlier Rails versions, the extraction of the Websocket server (the event loop currently based on `nio4r`) with a clear API, could both make maintenance easier and allow for performance improvements (i.e., by utilizing a platform specific optimized server). What is your opinion? Should the ActionCable server be extracted from ActionCable? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
