Live data from Hacker News

Asynchronous ruby framework for websockets, eventsource and streaming

cramp.in

11–15 of 15 posts

Re: Asynchronous ruby framework for websockets, eventsource and streaming

#11

1. Does this work with Rails? 2. Generally, the "Hello World" for a real-time framework is a simple chat application.

1. It can work within the same Rails process if you're using async Rails.

2. http://cramp.in/examples two chat apps there. But I don't have a live demo running.

Re: Asynchronous ruby framework for websockets, eventsource and streaming

#12
Goliath has a websockets branch and also supports eventsource and streaming pretty easily. If it's something you need, definitely look into Goliath as well.

http://www.igvita.com/2011/08/26/server-sent-event-notificat... https://github.com/postrank-labs/goliath/tree/websockets

Re: Asynchronous ruby framework for websockets, eventsource and streaming

#13

Goliath has a websockets branch and also supports eventsource and streaming pretty easily. If it's something you need, definitely look into Goliath as well. http://www.igvita.com/2011/08/26/server-sent-event-notificat... https://github.com/postrank-labs/goliath/tree/websockets

Personally, I think Cramp's interface is a lot better than Goliath when it comes to streaming, because everything is streaming in Cramp. YMMV. https://github.com/lifo/cramp/blob/master/examples/sse/serve... in case you want to compare. Also, goliath websockets branch looks outdated.

FWIW, I do like Goliath. More async solutions in Ruby the better!

Re: Asynchronous ruby framework for websockets, eventsource and streaming

#15
post #6

I would really love to see some perf comparisons vs C# or Java.

I'd love to see it too! However, I do think the comparisons should be about the ability handle the number of open connections seamlessly and not req/sec. And relevant memory/cpu usages.

Agreed - do you have any anecdotal evidence of how it performs comparatively to say, Erlang or node?
Post reply on HN