title: Catalyst comet/long polling
body: <p>I've been battling this question for a while, as surely many Catalyst programmers did as well. Now we see some examples from John about nonblocking applications running with Twiggy.
  But I think Twiggy is not the best option to run my whole application. So clearly I want to decouple it and run my app on nginx for example and forward my comet traffic to the Twiggy.</p>
  
  <p>The main problem I see is the authentication. There are several possible options here, that I see:</p>
  
  <ol>
  <li>move authentication to a front-end server</li>
  <li>move authentication to a separate catalyst app</li>
  <li>use session ids when communicationg with a Twiggy</li>
  <li>?? Using Plack sessions ??</li>
  </ol>
  
  <p>First option is not really good, because it does not give me flexibility when changing a front-end server. The second one has also considerable expenses. And the third one I think is the easiest one, taking into account that the Catalyst::Plugin::Session::Store::DBI is used as a session backend. </p>
  
  <p>These are the options that came to my mind. Surely I miss something. So maybe someone encountered the same problems? I would be grateful to anyone who can give me a hint or expand my view on this problematic. It will be also helpful to see pros and contras about each option, as well as some hints about them.</p>