Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47475
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.223 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=KiesjCIO34XPQ676ENXKRI+xLrqjr/xE+oNRZ6Z/JVoeXYQrGcDfWy5euzBbDcQnWw
         el0VtOzYDLJJ2VUciVauhlOp9W4fsh99pyLlId0w+3SxdHR9U+18GOrC8qvgn1h3iit0
         Nnsvcrt12wF+gAuacfbEyl/ATFX/1h8Ykt2ms=
MIME-Version: 1.0
In-Reply-To: <62211B4874BB4DD0A9628107EC69B06A@pc>
References: <98b8086f1003220751j73a8414es89b9b469c46f6630@mail.gmail.com>
	 <98b8086f1003220822s47665f87x696b70e9c13dadbd@mail.gmail.com>
	 <f658eb6f1003220841p5517561cpd044d4389f7a3b63@mail.gmail.com>
	 <98b8086f1003220855ya52c266g8dc4cb866ed451ea@mail.gmail.com>
	 <98b8086f1003221054j161316barf9a772da78f4ca85@mail.gmail.com>
	 <1855ED34-B6FA-4B74-B603-5A0D0A47A5A6@macvicar.net>
	 <98b8086f1003221137v1942fba6tee987fe3b4ff4715@mail.gmail.com>
	 <EDAFB0D4-2748-429C-8C11-F6BECA8A018D@macvicar.net>
	 <98b8086f1003221227w476f4e5eo82b790dfe16770b2@mail.gmail.com>
	 <62211B4874BB4DD0A9628107EC69B06A@pc>
Date: Tue, 23 Mar 2010 10:50:15 +0100
Message-ID: <98b8086f1003230250q316fdbdbye9ea168ab9c18b6c@mail.gmail.com>
To: Stan Vassilev <sv_forums@fmethod.com>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [PATCH] Raise warning first on "Maximum execution time 
	exceeded"
From: troelskn@gmail.com (troels knak-nielsen)

Hi Stan.

On Tue, Mar 23, 2010 at 8:47 AM, Stan Vassilev <sv_forums@fmethod.com> wrote:
> Thanks for your patch, but you're going to affect a whole group of users who
> do advanced logging and recovery in the shutdown phase. This is why these
> things have to be considered when they're first added.

How would they be affected? Current behavior would still be there.

> A grace period of 1 second seems sufficient on a pristine condition unused
> server, but when your server is loaded, a spike in load may cause a number
> of shutdown handlers to take more than 1 second, and stop middway running,
> causing a lot of unpredictability and trouble for those who rely on this
> feature.

So, you mean that a patch that fixes 90% of the cases, but leaves the
10%, is worse than no patch, because of the confusion it might cause?

I guess that could be a valid point; Is it a generally agreed-on
strategy for php?

-- 
troels