Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78434
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <544D65F7.8070807@sugarcrm.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> <CAHsEcH_m3MHq2qTa=zrtZs9Ub1SoimeHJ1A9s9Efwdu6U9APJw@mail.gmail.com>
 <544D65F7.8070807@sugarcrm.com>
Date: Tue, 28 Oct 2014 09:15:53 -0700
Message-ID: <CAHsEcH8VBSotZuLAM3NopLXQKEWrr6DqK2HQaoJOAKUshjii5A@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Zeev Suraski <zeev@zend.com>, 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=f46d043d671362ea3605067df765
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: catch.dave@gmail.com (Dave)

--f46d043d671362ea3605067df765
Content-Type: text/plain; charset=UTF-8

1. Sure, but the frustrating thing is that the C code (for mime-parsing) is
already there and just not being used for non-POST methods. Why make
everyone use pecl/framework code that duplicates what exists in PHP already
(albeit for POST only)?

2. You're right. That would be too many. That's why adding a single new
variable of $_FORM/BODY/foo would work for everything (including POST). Of
course, $_FILES (whose name is already method-agnostic) should be populated
too and not restricted to POST only.

On 26 October 2014 14:21, Stas Malyshev <smalyshev@sugarcrm.com> wrote:

> Hi!
>
> > 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
>
> It is true that PUT data need to be parsed, however it is not true you
> have to implement MIME parsing from scratch. There are frameworks that
> implement that. Not everything must be written in C. But if you want C,
> doesn't pecl/http already have the required bits?
>
> > 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).
>
> There are a lot of HTTP verbs - PUT, DELETE, TRACE, PATCH... And what if
> you want to do WebDAV? Wouldn't having separate superglobal for each be
> taking it a bit too far?
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
>

--f46d043d671362ea3605067df765--