Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78351
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <57b7a3681d6c2c7ae123c8921b2d19d6@mail.gmail.com>
References: <CAKOpQSwS=Xck41sQQyEYGG8L3VHq+fRWjy0dDorbwZaVWMLCow@mail.gmail.com>
 <776669CE-9E8C-4069-9834-C7275CCA0EF4@ajf.me> <CAKOpQSwRtSU1LNmftyY1b09SONBCfwS-qiMK4gct6uFiW3CSjw@mail.gmail.com>
 <CAPhkiZwb13FmX+sQLx0Ki52KuwJ4HWTj-84UqcZq3GYPFL8Tnw@mail.gmail.com>
 <E8F7D721-767C-4E6E-B0BB-F0DEFEB308B2@ajf.me> <CAF9U7z_0cgwWFEoShU9rJhoOZttztcZk_NAqoXnSuAro-w3kew@mail.gmail.com>
 <8CB055D4-F164-4DF3-B019-684BAE7E016E@ajf.me> <543D47C1.9050009@lerdorf.com>
 <etPan.543d4c0e.216231b.12d@Mikes-iMac.local> <543D4CE1.5000109@lerdorf.com>
 <543D6864.10508@gmail.com> <543D85E6.2020507@lerdorf.com> <CAKOpQSyTSZeXppZ-f9OeNfA9=Q58jte1fH6zcuzxYZ+qK7-6JA@mail.gmail.com>
 <57b7a3681d6c2c7ae123c8921b2d19d6@mail.gmail.com>
Date: Sun, 26 Oct 2014 11:30:50 -0700
Message-ID: <CAHsEcH_m3MHq2qTa=zrtZs9Ub1SoimeHJ1A9s9Efwdu6U9APJw@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Kris Craig <kris.craig@gmail.com>, Rasmus Lerdorf <rasmus@lerdorf.com>, 
	Rowan Collins <rowan.collins@gmail.com>, PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bb708a03e7eaa0506579efd
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: catch.dave@gmail.com (Dave)

--047d7bb708a03e7eaa0506579efd
Content-Type: text/plain; charset=UTF-8

> there's really nothing missing from PHP today to enable successful & easy
implementation of RESTful interfaces.

Zeev,

I could not create a REST interface that accepted "multipart form data" in
uploading a file and form data in one PUT request.
This is a valid part of a RESTful interface, yet PHP does not provide
parsed data and file data for PUT like it does for POST (in the form of
$_FILES and $_POST).

The only way to do this in PHP now is write a userland function that parses
multipart form data, which is non-trivial. I had written one, but would
rather rely on the more-well tested parser which exists in PHP itself for
POST. (A side-note: in my case it was deemed less risky to employ a
load-balancer hack instead).

Having the ability to access the data provided in $_POST for other methods
is ideal (by whatever means: $_PUT, $_FORM, get_parsed_form_data(), etc).

Dave.


On 14 October 2014 14:56, Zeev Suraski <zeev@zend.com> wrote:

> > Personally, I like the idea of using more appropriately named aliases,
> > particularly if they're roughly the same number of characters.  However,
> > we
> > would need to allow at least several years for people to adopt the new
> > globals before deprecating $_GET and $_POST.  Ultimately, they will
> either
> > need to be deprecated or the $_PUT and $_DELETE aliases will need to be
> > added, otherwise the issue I raised would remain unresolved.
>
> Kris,
>
> Don't get this the wrong way, but $_GET and $_POST are not going to be
> deprecated.
>
> Whether or not we need $_PUT or $_DELETE is a separate, independent
> question
> from the axiom that $_GET and $_POST are here to stay.  Personally, I don't
> think they make sense as Rasmus pointed out that $_GET and $_POST were
> never
> about HTTP methods but form methods, and there's really nothing missing
> from
> PHP today to enable successful & easy implementation of RESTful interfaces.
>
> Zeev
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--047d7bb708a03e7eaa0506579efd--