In short, in order to provide a proper REST service that supports
multipart
form data, we need someway to parse data sent via PUT (data is available
via php://input, but it needs to be parsed).
Multipart entity parsing is fairly straightforward. You could easily write
a parser in userland to
On 24 September 2013 16:59, Daniel Lowrey rdlow...@gmail.com wrote:
The bigger issue here is that the superglobals are a leaky abstraction. Any
HTTP request method is allowed to have an entity body, so should we also
create $_PATCH and $_PUT and $_ZANZIBAR to handle less-frequently used
Thanks Daniel. My thoughts on your response:
Where does it stop? This is the problem I see with all the requests to
support for PUT similarly to POST.
Right here with PUT. Providing a RESTful interface is hugely common and $_PUT
is the only one missing to complete REST. PUT is the glaringly
Let me be clear: I'm not suggesting we should ignore useful functionality
because of poor design decisions made in the past but I am saying that we
should avoid compounding those mistakes by building on top of them. Would a
$_PUT superglobal be helpful? Sure. But is it a good solution to
On 24/09/2013 17:12, Daniel Lowrey wrote:
An inability on your part to write working code doesn't equate to PHP
should implement this for me
I am not the tone police, but I don't think such comments are helpful.
Let me be clear: I'm not suggesting we should ignore useful functionality
I am not the tone police, but I don't think such comments are helpful.
Hey, sorry all :)
Not trying to suggest anyone is incapable of writing working code (I know I
am from time to time). I was simply ticking off my objections to the
arguments presented. I'm in favor of kinder, gentler internals
