Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78826
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.178 as permitted sender)
MIME-Version: 1.0
Date: Thu, 6 Nov 2014 17:54:18 -0500
Message-ID: <CAL+t6cGGatDPa89boDT-2jDTwTZEz-LMfp7CLCGcjNNX1W9vSw@mail.gmail.com>
To: Sanford Whiteman <figureonecpr@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bf0d0f6898d560507389319
Subject: Re: New Standardized HTTP Interface
From: theanomaly.is@gmail.com (Sherif Ramadan)

--047d7bf0d0f6898d560507389319
Content-Type: text/plain; charset=UTF-8

On Thu, Nov 6, 2014 at 6:42 AM, Sanford Whiteman <figureonecpr@gmail.com>
wrote:

> Prove I "believe a multipart/form-data mime cannot be sent along with a
> PUT request" using messages I have sent to this list.  You are basically
> lying for effect at this point. I never said that, took pains to explain
> that I am not saying that, gave examples utterly to the contrary... yet you
> make stuff up anyway.



I'm done with this. I hope you find a more honest way to defend your
> proposals in the future.

-- S.


I'm honestly not sure what it is you are saying anymore. All I know is that
so far you're opposed to populating a super global like $_POST or $_FILES
with data from a multipart request that uses the PUT verb rather than POST,
based on this statement you made early on in the thread:



> If you're PUTing such POSTful content-types for any reason other than
> storing the entire resource, you're doing HTTP wrong.



Here, you are clearly implying that the content-type is somehow associated
with POST and not PUT and that one should never attempt to do anything
other than store the entirety of the enclosed entity upon receiving a PUT
request. Otherwise we're violating the HTTP specification. This can be
clearly inferred from these words.

The intent is to store the entity, yes, but what is so bad about allowing
people to process information from that entity before hand? Certainly that
is the entire point of PHP, no? You receive some HTTP request through PHP
so that you can somehow do some pre-processing on it before serving up the
response. Otherwise you'd just have your webserver deal with it if it was
considered a static asset.

I certainly have no ill intentions. I'm neither a liar nor have I brought
your ethics into question during this discussion. I assume that people have
the best of intentions until they prove otherwise. So I would greatly
appreciate it if you refrained from doing so yourself and began to assume
that we all have the best of intentions here.

If your argument isn't that one should NOT send multipart/form-data
content-type along with a PUT request, or that PHP should not attempt to
populate the parts of the request in super globals, than what is it? Please
help me to understand your opposition to this proposal so that we can reach
some consensus about its validity.

Certainly we can either learn to be civilized in our technical discussion
or we can refrain from participating in it. Making this person isn't going
to benefit the PHP community in any way.

Lastly, I would like to say that I sincerely appreciate your time and
contributions to this discussion and I consider them valuable regardless of
whether or not I fully agree with you, personally. I only wish to come away
from this discussion with what is in the best interest of the community at
large and not my own individual interests. I hope that's clear and
alleviates any misconceptions of my intent to aspire for personal gain.

--047d7bf0d0f6898d560507389319--