Support for the Rack Websocket extension draft? about agoo

[ohler55]

Ahh, The Iodine owner. You've got a fast server there. I like the multiple worker approach for when a shared state is not needed. Agoo and Iodine are neck and neck on performance.

I do plan on adding support for websockets. I have a library I wrote and have used on another projec (piperpushcache.com)t. I wasn't sure how much demand there was for it so I wasn't in a big hurry. I'll look at the links you provided and learn more about where the demand is. I had read somewhere that the plan to support websockets was to hijack the connection and then leave it up to the app. I'm with you in thinking that is a cop out and some common approach in the server would be better.

My favorite pub/sub is NATS. A friend of mine wrote that and I have used it on projects at work and for play. It has a Ruby API as well C and quite a few others. I'm not sure how that relates to websockets with support or at least not sure how it would directly relate. I could certainly see another gem or bit of code that bridges the network pub/sub component to the websockets component. I do like a pub/sub model for websockets though.

I am currently working on two dev stream, Agoo and OpO which is closed source for now. OpO is a fast JSON database. My plan for clustering is to span multiple machines and use the OpO database for shared state. Thats a little ways off though.

I'm glad you reached out. We can take more discussions via email but lets leave this issue open as a place holder for websocket support. I'll update it with comments related to that as I move along.

[ohler55]

Supported in release 2.0.0. Rack PR is pending.