[Mongrel] mongrel and long lived connections

Joseph McDonald superjoe at gmail.com
Tue Dec 5 17:30:23 EST 2006


well i think i found the problem...  I think it's my browser.  I could
not open more than 1 connection with firefox, but if i opened msie and
opera on the url, the data came streaming on down simultaneously.

sorry for the false alarm!
-joe


On 12/5/06, Joseph McDonald <superjoe at gmail.com> wrote:
> OK.  I'm just trying to understand why/where mongrel is blocking when
> more than 1 request comes in for a particular uri.  I'm thinking there
> may be something different with this particular httphandler.  Or maybe
> not... maybe mongrel can't service more than 1 request for a
> particular uri at a time.
>
> It's interesting that more than 1 can run at a time, you just need to
> associate them with different uri's.  I'd like to find out why that
> is, and if that's changeable.
>
> -joe
>
> On 12/5/06, Vishnu Gopal <g.vishnu at gmail.com> wrote:
> > 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 <superjoe at gmail.com> 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 <david at vrensk.com> wrote:
> > > > On 12/5/06, Joseph McDonald <superjoe at gmail.com> 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
> > > > Mongrel-users at rubyforge.org
> > > > http://rubyforge.org/mailman/listinfo/mongrel-users
> > > >
> > > >
> > > _______________________________________________
> > > Mongrel-users mailing list
> > > Mongrel-users at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/mongrel-users
> > >
> >
> >
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
> >
>


More information about the Mongrel-users mailing list