Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51048 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40675 invoked from network); 16 Dec 2010 13:51:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2010 13:51:14 -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.213.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.213.170 mail-yx0-f170.google.com Received: from [209.85.213.170] ([209.85.213.170:60620] helo=mail-yx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/70-36789-F491A0D4 for ; Thu, 16 Dec 2010 08:51:12 -0500 Received: by yxi11 with SMTP id 11so1737834yxi.29 for ; Thu, 16 Dec 2010 05:51:09 -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=baej+zIBzizuK1LI8SzUDSjzkkETVVwKPVf6goAQ2D8=; b=TeJfeCT0hTJ2+EEFrWlkKHzuNez1vvUGrqtH5qw+iF8l2pH2dxvTQ0qdz1XoQokxWE bRCP+5NqWyKMUSyFOeAWrPXTSqWpUSrW9zK6fVwkXaEN/lvC8xqIsfxTo7WuCvVJ0MgR v9ndBAZukAtDp6TEwz+L2wz4hfTtd5eoZRxIs= 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=qAlB+RRwd4bi5slGV+ZaLepMLrahTRQ/6siqUnZQYP4UkO0uNciVlPcsjP9Kd6BRO1 9YATIhI5W9Gh1HeHcYU0lSpZpMAxR3bHhWMLdEbxRQDumap7Nc8f2el3HolQs6lqQtqj HwnUZO2mkF+QAqRcQ35nzEAB2cN1gydHVFCgU= MIME-Version: 1.0 Received: by 10.90.90.3 with SMTP id n3mr739814agb.141.1292507469100; Thu, 16 Dec 2010 05:51:09 -0800 (PST) Sender: tyra3l@gmail.com Received: by 10.90.53.4 with HTTP; Thu, 16 Dec 2010 05:51:08 -0800 (PST) In-Reply-To: References: <6b2ba5e56d64910c49bb431ba1e36e17@nebm.ist.utl.pt> Date: Thu, 16 Dec 2010 14:51:08 +0100 X-Google-Sender-Auth: MSMlQJTxiKLHCBRMn_NvEpPQc9I Message-ID: To: Pierre Joye Cc: Gustavo Lopes , internals@lists.php.net Content-Type: multipart/alternative; boundary=0016361e87d890b81104978758e7 Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing From: info@tyrael.hu (Ferenc Kovacs) --0016361e87d890b81104978758e7 Content-Type: text/plain; charset=UTF-8 On Thu, Dec 16, 2010 at 2:16 PM, Pierre Joye wrote: > There are a lot of values to disable POST completely. That's also why > thinking the option you are proposing while keeping in mind the whole > picture makes sense. > > There are different existing modes and one or two new modes (to be > introduced, like disabling POST). Having a clean way to choose which > mode should be used for a request makes sense and will improve the > user experience. Right now and as shown the confusing discussions on > IRC (or partially here) shows that the current situation is a mess. > > Again, I'm not saying that the idea behind this patch is bad, only > that there is a better way to do it while being less confusing and > making the whole thing cleaner to define. > > http://en.wikipedia.org/wiki/Nirvana_fallacy If you think that there is a better alternative, please write an RFC and or a patch, but I don't think that we should give up a good idea which has support and patch for a vague idea, which is maybe better, but nobody going to put effort in it to write RFC, write the patch, etc. but that is my 2 cents of course. Tyrael --0016361e87d890b81104978758e7--