Evan,
I believe that optional with default being to drop the connection
would be best in this case. It will serve the 98% case just fine and
for those who are more demanding they can opt in.
The rest look like a good set for a 2.0 release to me.
~Wayne
On Nov 18, 2008, at 00:49 , Evan Weaver wrote:
Optional is a good compromise.
Evan
On Tue, Nov 18, 2008 at 12:36 AM, Zed A. Shaw <[EMAIL PROTECTED]>
wrote:
Very cool, nice work. One small comment...
On Mon, Nov 17, 2008 at 03:32:33PM -0500, Evan Weaver wrote:
Hi Mongrels,
- Error code instead of connection-close, as discussed earlier
With this do you mean returning one of the many error codes in an
HTTP
response when the server is overloaded?
I would recommend against that if that's the case. In theory it's
nice
to return an error code to clients that could be waiting. In
practice,
your queue is already overloaded, so taking more time to send a
response
to clients only adds to the problem. In a modern system this isn't
such
a big deal, but in Ruby it becomes a mess because of the file id
limits
in the select loop.
I'd say, if you add that, make it optional to turn it off and be
prepared with a FAQ about it in case people have problems.
Have fun.
--
Zed A. Shaw
http://freehackersunion.org/
_______________________________________________
Mongrel-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-development
--
Evan Weaver
_______________________________________________
Mongrel-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-development
_______________________________________________
Mongrel-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-development
