Re: [Zope-dev] Timing the opening of network ports
--On 29. August 2006 18:50:43 +0200 Dieter Maurer [EMAIL PROTECTED] wrote: Jens Vagelpohl wrote at 2006-8-28 20:14 +0200: On 28 Aug 2006, at 19:19, Andreas Jung wrote: Some time ago the following patch was proposed to control the timing for opening the socket ports upon startup: http://mail.zope.org/pipermail/zope-dev/2005-November/025709.html I propose to adapt the patch for Zope 2.11 since it is pretty useful especially when you deal with loadbalancers and have Zope instances that take a lot time for starting up (e.g. Plone :-)). Any objections? +1 If you have load balancers that only look for open ports (or a single instance with no load balancers even) this will improve the user experience for people who hit the site upon startup. IMHO it's more helpful to get a connection refused reply in a browser than a browser that sits and sits and sites... Can we make this configurable? The patch fast-listen patch is already available on the trunk. However I don't have plans for any further work in that area. -aj pgpjZ4ImdeX8y.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Timing the opening of network ports
Jens Vagelpohl wrote at 2006-8-28 20:14 +0200: On 28 Aug 2006, at 19:19, Andreas Jung wrote: Some time ago the following patch was proposed to control the timing for opening the socket ports upon startup: http://mail.zope.org/pipermail/zope-dev/2005-November/025709.html I propose to adapt the patch for Zope 2.11 since it is pretty useful especially when you deal with loadbalancers and have Zope instances that take a lot time for starting up (e.g. Plone :-)). Any objections? +1 If you have load balancers that only look for open ports (or a single instance with no load balancers even) this will improve the user experience for people who hit the site upon startup. IMHO it's more helpful to get a connection refused reply in a browser than a browser that sits and sits and sites... Can we make this configurable? Earlier Zope versions had bound the ports rather late. When later Zope versions bound the ports early, I was quite happy. Unlike you, I prefer when the browser waits until Zope has come up over me having to reload manually until it finally is ready... -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Timing the opening of network ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28 Aug 2006, at 19:19, Andreas Jung wrote: Some time ago the following patch was proposed to control the timing for opening the socket ports upon startup: http://mail.zope.org/pipermail/zope-dev/2005-November/025709.html I propose to adapt the patch for Zope 2.11 since it is pretty useful especially when you deal with loadbalancers and have Zope instances that take a lot time for starting up (e.g. Plone :-)). Any objections? +1 If you have load balancers that only look for open ports (or a single instance with no load balancers even) this will improve the user experience for people who hit the site upon startup. IMHO it's more helpful to get a connection refused reply in a browser than a browser that sits and sits and sites... jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE8zJrRAx5nvEhZLIRAqUTAJ4hPrqildFLXLg+vdYIA0F26J/o1gCgpBZT bvhVObipCKUessLOC1ANc/Q= =D5Fx -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
