On 12/5/06, Joseph McDonald [EMAIL PROTECTED] wrote:
Hi,
I found this article
http://cyll.org/blog/tech/2006-08-09-themongrelcomet.html on mongrel
and COMET very interesting.
I ran the code, and it worked just as Christopher explained. The one
thing I don't understand is why mongrel can
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
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
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
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.
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 [EMAIL PROTECTED] wrote:
On Tue, 5 Dec 2006 13:08:14 -0800
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
