-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jung wrote:
--On 29. August 2006 18:37:45 +0100 Chris Withers <chris@simplistix.co.uk> wrote:
Tres Seaver wrote:
Unlike you, I prefer when the browser waits until Zope has come up over me having to reload manually until it finally is ready...
The branch Andreas just merged leaves the "fast-bind" option on by default.
Cool, although I can't really see the use ;-)
The usecase is pretty simple: you have a loadbalancer and remove one backend Zope. The LB detects the removal and stops forwarding request. When the client comes back (means Zope opens the ports early) the LB will start forwarding to the client although it might take a while until the Zope instance is really up and ready to serve request. So by opening the ports late we are able to reduce the latency and avoid pending requests.
The other reason for wanting "early binding" to the ports is if the ports are in the "reserved for root" range (< 1024); in that case, the ports *must* be bound early, before dropping privileges to those of the "effective user". Tres - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE9ucV+gerLs4ltQ4RAt+9AJkBLjRKmZaRQWPq2iiKIRAZy+W2hwCfTeW/ FaLZGLsRx8J4JJHNPtnJxy4= =mir0 -----END PGP SIGNATURE-----