4 ms·
Rails in Realtime, Part 2
- marcamillion 14y agoLove this. This is actually quite timely for me. An app I am trying to build, involves a lot of real-time stuff and have been debating whether or not I should go to a client-side MVC. I am not too gung-ho on doing it, largely because at the core a lot of the functionality of the app is simple CRUD stuff. Then just a matter of updating elements of the app in real time. Is there a gem for Socket.IO?
- kellysutton 14y agoYes. https://github.com/lyondhill/socket.io-ruby-client https://github.com/lyondhill/socket.io-ruby-client
- marcamillion 14y agoIs this what you guys used, or did you use the regular client in some other way?
- kellysutton 14y agoThat is what we use in production.
- ludicast 14y agoUse sockjs instead of socket.io :). There is a rails gem for it, or you could use ruby on top of vert.x which also supports sockjs.
- joeycfan 14y agoBeen looking for this for a long time. Thanks.
- mje 14y agoGreat work Kelly. How much browser pain have you all had with data-attributes?
- kellysutton 14y agoSo far, no browser pain at all with the data-attributes. When dealing with numbers, you will often find yourself making many calls to parseInt(). Other than that, it's smooth sailing.
- mje 14y agoGreat thanks. So cool to see what you have done since the days at AutomaticDuck.
- marcamillion 14y agoWhere is your production app hosted? Heroku? AWS? Your own colo box?
- kellysutton 14y agoWe use Slicehost.