Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57949
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
Received-SPF: pass (google.com: domain of will.fitch@gmail.com designates 10.229.76.139 as permitted sender) client-ip=10.229.76.139;
Date: Wed, 22 Feb 2012 10:03:50 -0500
To: Michael Morris <dmgx.michael@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Message-ID: <8D8E9A0839FE464FBBDF2B499DAFA596@gmail.com>
In-Reply-To: <CAGovj_PbjoB78kXvZcaSkx3qQziMXX7ezVmzYSPHQbJL7uu7VA@mail.gmail.com>
References: <CAGovj_PbjoB78kXvZcaSkx3qQziMXX7ezVmzYSPHQbJL7uu7VA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4f4503d6_7c3dbd3d_6ecc"
Subject: Re: [PHP-DEV] $_PARAMETERS Super Global Object
From: will.fitch@gmail.com (Will Fitch)

--4f4503d6_7c3dbd3d_6ecc
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Personally, I don't like this.  We already have $_REQUEST which can accommodate GET, POST, and COOKIE. I believe it should be up to framework/API authors to implement there own methodologies behind accessing this data.  Additional functionality such as setting filters would be a part of that as well.  

That said, if you're serious about the idea, a RFC would be helpful in understanding the full extent that you're suggesting. 

-- 
Will Fitch


On Wednesday, February 22, 2012 at 9:57 AM, 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..
> 
> $_PARAMETERS
> ->get
> ->post
> ->cookie
> ->headers (The client http headers)
> 
> All of these would be array objects, and all would be read only and
> have these methods and properties
> 
> ->filtered: Copy of the array according to the current set filters of
> the object.
> ->setFilters(): Sets the filters of the input, an array with constant
> values for the allowed types.
> 
> And I'll stop there. The basic idea, to add a read only input hive
> with some basic object functionality for filtering.
> 
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
> 
> 



--4f4503d6_7c3dbd3d_6ecc--