[EMAIL PROTECTED] wrote:
Ian Bicking said:
I've had a few problems with SCGI 1.2. The attached patch:
* Fixes the connection retrying -- when addr wasn't reconstructed with
each retry, the second retry would always fail with Invalid Argument
error, not ECONNREFUSED. Probably increasing the retry delay *2 each
time is also too aggressive -- I like the idea of increasing the delay,
but probably not past 5 seconds.
Some (all?) of this stuff probably belongs in the Apache code as well,
Does it make the web server wait if the application server is not running?
I like the way mod_scgi gives an error immediately rather than waiting
ten seconds and then timing out as mod_webkit does.
Well, cgi2scgi was supposed to act like mod_webkit, it was just a bug
that it wasn't. Really the retrying should be a configurable value; at
the moment it is hardcoded. Retrying certainly the right way to do it
on a live site, since it lets you restart a server without losing any
requests; it's a matter of preference during development (though
personally I prefer retrying in development too, but maybe not retrying
quite as long).
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
_______________________________________________
Quixote-users mailing list
[email protected]
http://mail.mems-exchange.org/mailman/listinfo/quixote-users
