Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78853
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <545D3E66.6060202@sugarcrm.com>
References: <CAL+t6cGt8B+X4ptWbyo6zm_xoyBOJC4QeiH6DjCxHX11CPWm_g@mail.gmail.com>
	<CACwt+JcYMS=+3t3e_JLHbNx-mgxUceiPOws2GZn9_QZ4HEo4Uw@mail.gmail.com>
	<CAL+t6cHDLHjTE3JK0md=KZ=AnRns6iYxfphzA3qnShermVeOmg@mail.gmail.com>
	<1DDB6E05-3143-4A74-8B13-AF85222579BA@ajf.me>
	<CAL+t6cH92NgWnr-0gh9AfTxX_1r5Fd0=+M6SeZu53BT3nPHSEg@mail.gmail.com>
	<468730E8-4C38-49A3-A61A-59E107313D79@ajf.me>
	<CAL+t6cGPiqZXx2rQCzSV-PCzAAJtMWi6xteCU0GB0XjsB4wSpA@mail.gmail.com>
	<545C1823.8050404@sugarcrm.com>
	<CAL+t6cG+j7emBboNcnZi5wC6QtjFtmEcDGgsnA6sJVx9qpD41A@mail.gmail.com>
	<545D3E66.6060202@sugarcrm.com>
Date: Fri, 7 Nov 2014 17:11:27 -0500
Message-ID: <CAL+t6cHXPC40xiQWBW1Xrjhps2+vCCFXKJW8XY+tSyD+jtCU1A@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Andrea Faulds <ajf@ajf.me>, Patrick ALLAERT <patrickallaert@php.net>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bb047dc235d3005074c1861
Subject: Re: [PHP-DEV] New Standardized HTTP Interface
From: theanomaly.is@gmail.com (Sherif Ramadan)

--047d7bb047dc235d3005074c1861
Content-Type: text/plain; charset=UTF-8

On Fri, Nov 7, 2014 at 4:49 PM, Stas Malyshev <smalyshev@sugarcrm.com>
wrote:

> Hi!
>
>
> So the question here is how common is the case of PUT+mulitpart/form-data?
>


Well, that's what I'm trying to establish. Based on the information I have
available, there have been a few dated bug reports asking for this. There
are also a lot of forums questions found on github/stackoverflow/etc...
that apparently find this useful. How useful it is and how common the use
case is may not be enough, though. Based on your feedback I can definitely
see a lot of people making future feature requests to add support for
additional content-types and I really don't think the SAPI implementation
should necessarily start heading down that road. Only because based on this
discussion I fear that no one other than myself will be eager to support
it. I'd rather not introduce cruft into PHP if I can avoid it.

I'll gather some more data and perhaps see if an initial implementation can
prove extensible enough.

--047d7bb047dc235d3005074c1861--