3 ms·
Using heroku in pre-alpha meant we couldn't use websockets. Since we were very used to Heroku, we figured we'd just accept this limitation and work around it (w
by railsjedi 16y ago
Using heroku in pre-alpha meant we couldn't use websockets. Since we were very used to Heroku, we figured we'd just accept this limitation and work around it (with PusherApp). Turned out to be a great decision since we never would have had time to implement websockets I don;t think. It's definitely not hard with Node, but it does take some thought and configuration.
For server->client event triggering, PusherApp has got to be the easiest possible solution out there. Also had really nice documentation with a quick getting started example.
- franck 16y agoFYI we used Socket.IO-Node for our NodeKO app. It didn't require any time or configuration at all - and I had zero experience with node.js prior to the first day of the competition. Most of all, it comes with a client library socket.io.js which has nice fallbacks for browsers that don't support websockets yet. I highly recommend it!
- smoody 16y agoThanks for the response and for the PusherApp lead. I'm going to try it out myself.