<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: michael-carter</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/michael-carter.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-07-29T09:48:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>Hookbox</title><link href="https://simonwillison.net/2010/Jul/29/hookbox/#atom-tag" rel="alternate"/><published>2010-07-29T09:48:00+00:00</published><updated>2010-07-29T09:48:00+00:00</updated><id>https://simonwillison.net/2010/Jul/29/hookbox/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://hookbox.org/"&gt;Hookbox&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
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”.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://cometdaily.com/2010/07/26/a-fast-introduction-to-hookbox/"&gt;Comet Daily&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/comet"&gt;comet&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/michael-carter"&gt;michael-carter&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/php"&gt;php&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rails"&gt;rails&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/webhooks"&gt;webhooks&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recovered"&gt;recovered&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hookbox"&gt;hookbox&lt;/a&gt;&lt;/p&gt;



</summary><category term="comet"/><category term="django"/><category term="javascript"/><category term="michael-carter"/><category term="php"/><category term="rails"/><category term="webhooks"/><category term="recovered"/><category term="hookbox"/></entry><entry><title>Quoting Michael Carter</title><link href="https://simonwillison.net/2008/Feb/3/comet/#atom-tag" rel="alternate"/><published>2008-02-03T22:04:36+00:00</published><updated>2008-02-03T22:04:36+00:00</updated><id>https://simonwillison.net/2008/Feb/3/comet/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://cometdaily.com/2008/01/30/not-a-fancy-name/"&gt;&lt;p&gt;Let me be again clear here that Comet isn’t a new single technique. Rather, it’s a combination of existing push technologies with further research into new methods that together provides a robust framework for pushing data to all clients on modern networks.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://cometdaily.com/2008/01/30/not-a-fancy-name/"&gt;Michael Carter&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/comet"&gt;comet&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/michael-carter"&gt;michael-carter&lt;/a&gt;&lt;/p&gt;



</summary><category term="comet"/><category term="javascript"/><category term="michael-carter"/></entry></feed>