Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67611
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50FC9AC5.9070407@sugarcrm.com>
References: <50FC9AC5.9070407@sugarcrm.com>
Date: Mon, 3 Jun 2013 13:40:17 +0200
Message-ID: <CAH-PCH76JQ5qixAeOpkYFOeo9wnh8HiXB14kB0GQgodzYpGQQQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bdc05e8bc41cf04de3e6dc9
Subject: Re: [PHP-DEV] [VOTE] CURLFile uploading API
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7bdc05e8bc41cf04de3e6dc9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 21, 2013 at 2:32 AM, Stas Malyshev <smalyshev@sugarcrm.com>wrot=
e:

> Hi!
>
> I've started a vote on CURLFile RFC:
> https://wiki.php.net/rfc/curl-file-upload#vote
>
> Please vote.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Hi Stas,

I recently gave a presentation on the upcoming php version, and somebody
asked why did we introduce an OOP way for this when everything else in
ext/curl is procedural.
It seems that the OOP aproach was proposed first, and the procedural
alternative was added a week later, which seems to be a little bit odd.
Is there any particular reason for this?



--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7bdc05e8bc41cf04de3e6dc9--