Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36597 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32279 invoked from network); 27 Mar 2008 00:05:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Mar 2008 00:05:35 -0000 Authentication-Results: pb1.pair.com header.from=johannes@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.163 as permitted sender) X-PHP-List-Original-Sender: johannes@php.net X-Host-Fingerprint: 83.243.58.163 mail4.netbeat.de Received: from [83.243.58.163] ([83.243.58.163:60508] helo=mail4.netbeat.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 34/5B-47041-FC4EAE74 for ; Wed, 26 Mar 2008 19:05:35 -0500 Received: (qmail 12145 invoked by uid 507); 27 Mar 2008 00:05:31 -0000 Received: from unknown (HELO ?192.168.1.102?) (postmaster%schlueters.de@82.135.85.188) by mail4.netbeat.de with ESMTPA; 27 Mar 2008 00:05:31 -0000 To: "\"Pierre Joye\"" Cc: Felipe Pena , internals@lists.php.net In-Reply-To: References: <1206536686.5423.13.camel@felipe> <1206574472.11056.29.camel@goldfinger> <1206575656.11056.41.camel@goldfinger> Content-Type: text/plain; charset=utf-8 Date: Thu, 27 Mar 2008 01:05:30 +0100 Message-ID: <1206576330.11056.44.camel@goldfinger> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-3.fc8) Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Re: Backporting to 5_3 From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Thu, 2008-03-27 at 01:01 +0100, "Pierre Joye" wrote: > On Thu, Mar 27, 2008 at 12:54 AM, Johannes Schlüter wrote: > > > > > And compile time JIT is fine as long as we don't have to care for > > encoding, right? So this change won't be needed in 5.3. > > Except when one sends a xxMB post that you are not expecting and will > not use. But that has been so for years, too bad though, 5.3 is the > perfect time for such thing. which is handled by post_max_filesize and as long as we don't add error handling it doesn't make a difference if that happens at compile- or runtime. johannes