No, really. Ok so what happened here is that we had an in-house thing that did the same as this in Ruby that we made prior to socket.io becoming the Next Big Thing. It had some issues but those are now resolved. There were a few other issues in socket.io at the time of the port that prevented us from going over; specifically some issues that we handled well that they didn't at the time yet.
Those are probably all resolved and porting may be an easier and more sensible task now given that. In fact, there's a number of ways to pull this off using some pretty fun technologies out there without a port. But if you'd like to pick up where we left off here, then I encourage you to do so.
Feel free to contact me chris @ (the name of this user) . com. Thanks!
This project is:
- A ruby re-interpretation of https://github.com/LearnBoost/socket.io
- Meant to be in near sync with the HEAD at LearnBoost/socket.io; although the commit dates may not match up.
- Meant to be a rack-based ruby alternative with as few requirements as possible to accomodate large existing infrastructures.
For convenience, the necessary files below are included in the dep directory in the repository.
- node.js core EventEmitter
- node.js core http
- npm of policyfile
- some core JS routines implemented in Ruby
Since these libraries are being written in response to this project, it can be assumed (2011-09) that the versions in the repository here are the relevant ones neede and will be updated appropriately.
- A webserver (rainbows! or Thin are good)
- node_modules imported directory from socket.io
- Wrote in Ruby 1.8.7-p334 on Ubuntu 10.04. That's the testing ground too; your mileage may vary.
- A number of ancillary libraries had to be created and maintained to reach the design goal.
- 2011-09-05 Updated to 0.8.3, almost getting the nop
- 2011-08-25 Handshaking working
- 2011-08-23 Bootstrapping right
- 2011-08-18 Still working on the other libraries.
- 2011-08-11 Not done yet; don't expect it to work. It's really close though.