title: Django / Comet (Push): Least of all evils?
body: <p>I have read all the questions and answers I can find regarding Django and HTTP Push.  Yet, none offer a clear, concise, beginning-to-end solution about how to accomplish a basic "hello world" of so-called "comet" functionality.</p>
  
  <p>First question (1):  To what extent is the problem that HTTP simply isn't (at least so far) made for this?  Are all the potential solutions essentially hacks?</p>
  
  <p>2) What's the best currently available solution?  </p>
  
  <ul>
  <li>Orbited?</li>
  <li>Some other Twisted-based solution?  </li>
  <li>Tornado?  </li>
  <li>node.JS?  </li>
  <li>XMPP w/ BOSH?</li>
  </ul>
  
  <p>Some other solution?</p>
  
  <p>3) How does nginx push module play into this discussion?</p>
  
  <p>4) Which of these solutions require replacement of the typical mod_wsgi / nginx (or apache) deployment model?  Why do they require this?  Is this a favorable transition in any case?</p>
  
  <p>5) How significant are the advantages of using a solution that is already in Python?</p>
  
  <p>Alex Gaynor's presentation from PyCon 2010, which I just watched on blip.tv, is amazing and informative, but not terrifically specific on the current state of HTTP Push in Django.  One thing that he said that gave me some confidence was this:  Orbited does a good job of abstracting and simulating the concept of network sockets.  Thus, when WebSockets actually land, we'll be in a good place for a transition.  </p>
  
  <p>6) How does HTML5 Websockets differ from current solutions?  Is Gaynor's assessment of the ease of transition from Orbited accurate?</p>