3 ms·
Really interesting and (should the authors read this) thanks a ton for sharing it. I am curious about one thing. I sort-of already know the answer, but will ask
by smoody 16y ago
Really interesting and (should the authors read this) thanks a ton for sharing it. I am curious about one thing. I sort-of already know the answer, but will ask anyway: I saw in the post that you used Pusher for handling your realtime updates across clients (looks like a very cool service, btw). Isn't part of the strength of node.js and socket.io that things like push-based client/server apps are/should be trivial to implement without resorting to a third party service? If so, did you try? And do you know if other node knockout apps use pusher? (I assume that a: it saved a little time and b: was an easy way to get around Heroku's current connection limits, but want to know if there was more to it than that).
- railsjedi 16y agoUsing 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.