http://simonwillison.net/2010-07-29T09:48:00+00:00Simon Willison2010-07-29T09:48:00+00:002010-07-29T09:48:00+00:00https://simonwillison.net/2010/Jul/29/hookbox/#atom-tag

<p><strong><a href="http://hookbox.org/">Hookbox</a></strong></p> For most web projects, I believe implementing any real-time comet features on a separate stack from the rest of the application makes sense—keep using Rails, Django or PHP for the bulk of the application logic, and offload any WebSocket or Comet requests to a separate stack built on top of something like Node.js, Twisted, EventMachine or Jetty. Hookbox is the best example of that philosophy I’ve yet seen—it’s a Comet server that makes WebHook requests back to your regular application stack to check if a user has permission to publish or subscribe to a given channel. “The key insight is that all application development with hookbox happens either in JavaScript or in the native language of the web application itself”. <p><small></small>Via <a href="http://cometdaily.com/2010/07/26/a-fast-introduction-to-hookbox/">Comet Daily</a></small></p> <p>Tags: <a href="https://simonwillison.net/tags/comet">comet</a>, <a href="https://simonwillison.net/tags/django">django</a>, <a href="https://simonwillison.net/tags/javascript">javascript</a>, <a href="https://simonwillison.net/tags/michael-carter">michael-carter</a>, <a href="https://simonwillison.net/tags/php">php</a>, <a href="https://simonwillison.net/tags/rails">rails</a>, <a href="https://simonwillison.net/tags/webhooks">webhooks</a>, <a href="https://simonwillison.net/tags/recovered">recovered</a>, <a href="https://simonwillison.net/tags/hookbox">hookbox</a></p>