Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57953
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Michael Morris <dmgx.michael@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
In-Reply-To: <CAGovj_PbjoB78kXvZcaSkx3qQziMXX7ezVmzYSPHQbJL7uu7VA@mail.gmail.com>
References:
	 <CAGovj_PbjoB78kXvZcaSkx3qQziMXX7ezVmzYSPHQbJL7uu7VA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 22 Feb 2012 16:50:51 +0100
Message-ID: <1329925851.2179.1.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] $_PARAMETERS Super Global Object
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Wed, 2012-02-22 at 09:57 -0500, Michael Morris wrote:
> Before writing up a full RFC I want to put out a feeler on something.
> Currently we have several input parameter objects, chief among them
> $_GET, $_POST, $_REQUEST, $_SERVER (for the client HTTP headers).  All
> of them are arrays and legacy code sometimes writes to them.  Locking
> them as read only objects would cause a major BC break.
> 
> What if instead we had an Object called $_PARAMETERS which holds the
> read only copies of this data.  In addition, this would be the first
> superglobal object, able to perform some filtering of inputs.  Basic
> idea..

What's the benefit over filter_input()?

johannes