Random
Posted: 7 months ago (2009-12-28 19:26:57 UTC )
I pushed some new code for RailsGame, but it's speculative and reorg stuff. No real new functionality, though this paves the way for some of that. Mostly, I'm reducing the amount of duplicated stuff each RailsGame project needs to hold that's copied over from a master copy in the RailsGame gem itself.
Static assets in Rails engines would have solved most of this problem for me. It'll be good if they get around to adding that at some point.
There's a project called Web-Socket-JS, which is a WebSockets-compatible Flash-based server. It's going to take a very short time for FireFox to add WebSockets, and Chrome already has it. I don't see Safari being far behind.
IE, of course, will lag hideously. But Chrome Frame means I don't have to care. Besides which, having a Flash alternative is yet another reason I don't have to care.
So RailsGame should probably move toward WebSocketsJS rather than Juggernaut, because it's that or roll my own. Especially since I've had to roll so much of my own security for Juggernaut.
