If you read that wikipedia article, you'll note that Comet actually does want this to happen: one connection to be kept alive. Mongrel afai understand it is not meant to be used with keep-alive-ish sort of connections. Polling (via AJAX) would more often than not serve your purpose, and if it doesn't, a switch to Java or Cometd seems to be the way to go.
Vish On 12/6/06, Joseph McDonald <[EMAIL PROTECTED]> wrote:
I understand that rails is not thread safe, but this is not using rails or any part of rails. It just sets up a simple handler. but registering that handler seems to allow only one instance of that handler to run at a time. On 12/5/06, David Vrensk <[EMAIL PROTECTED]> wrote: > On 12/5/06, Joseph McDonald <[EMAIL PROTECTED]> wrote: > > I ran the code, and it worked just as Christopher explained. The one > > thing I don't understand is why mongrel can only handle 1 connection > > at a time. I thought that mongrel used a thread per connection. > > > The simple answer: Mongrel is multithreaded, but Rails is not thread-safe. > See question two in the FAQ: > http://mongrel.rubyforge.org/faq.html > > /David > > _______________________________________________ > Mongrel-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
_______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
