Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51045 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30458 invoked from network); 16 Dec 2010 12:55:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2010 12:55:00 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:58254] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/60-28099-12C0A0D4 for ; Thu, 16 Dec 2010 07:54:57 -0500 Received: by gyf2 with SMTP id 2so1691344gyf.29 for ; Thu, 16 Dec 2010 04:54:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=uDlVyFDRqbidIzxmlMEdjrMcpq1CCIvmBb91QvWdv5Q=; b=MAG7JhWBGWXw4XMsV9uqLly/RoI4p5VgJgNTs6ZzNA2M4/a77bs26VMWUI+d1zS0ce ljVqGb6/THFpHyhnik3w5A8aNFV8gUbJTkvhXfrPEyTj2axhHZGwC811kHGyA14/4/tg cTf8S1j8yLOH+lss6dt9UYSZ0booOlfzQBdfA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=piP/gQO3Tduxy8nMBKVVWaXzHKREV6f2O6R2VbbIcmlwf0SQ/1M5R+UwjHKmBf2Xzf AiM+6BfKI6/7OEwYsOj0m4OSerekZDFxtfKwyyNozvNZJCe59ovuL7Lg7FjPHTZZZxYS gok5P6ZSFAWXJcpvG+P9rCTYQDmPO/18x30uE= MIME-Version: 1.0 Received: by 10.90.71.18 with SMTP id t18mr679219aga.87.1292504094637; Thu, 16 Dec 2010 04:54:54 -0800 (PST) Sender: tyra3l@gmail.com Received: by 10.90.53.4 with HTTP; Thu, 16 Dec 2010 04:54:53 -0800 (PST) In-Reply-To: References: Date: Thu, 16 Dec 2010 13:54:53 +0100 X-Google-Sender-Auth: u7UNybWDA0WbSFcqmfcHSfii7Ig Message-ID: To: Pierre Joye Cc: Gustavo Lopes , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=00163630edad6e806c0497868f62 Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing From: info@tyrael.hu (Ferenc Kovacs) --00163630edad6e806c0497868f62 Content-Type: text/plain; charset=UTF-8 On Thu, Dec 16, 2010 at 1:47 PM, Pierre Joye wrote: > hi, > > On Thu, Dec 16, 2010 at 1:42 PM, Ferenc Kovacs wrote: > > > So currently we didn't talk about security measures, but performance > gains: > > If somebody wants to write a script, which handles big file uploads, but > > only writes it to somewhere (to file, or another stream), then currently > you > > have to allocate the memory for the post data twice(see the first email), > > which is very inefficient if you don't need the $_POST at all. > > yes, but that's something very confusing right now, the naming and the > other ways to access POST data. The goal of this idea is a good thing > to do, but the naming and its implementation are confusing (processing > vs reading vs used at all). > > agree, but it's not helping, if we introduce another similar idea for a whole different purpose to the conversation. :) the best would be a nice and clean RFC with the current status, the known problems, the suggested solutions, and a common and well-understood consistent naming convention. (disable POST processing, disable POST population, etc.) Tyrael --00163630edad6e806c0497868f62--