Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117973
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
In-Reply-To: <CANS-=pdrGap4ep=14DL97xPDOdM0+6eQszy8JE0c8+c8v8rxdQ@mail.gmail.com>
Date: Fri, 17 Jun 2022 11:18:42 +0100
Cc: Pierrick Charron <pierrick@php.net>,
 Larry Garfield <larry@garfieldtech.com>,
 php internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <8C82AFCA-710B-4F8F-AA25-87FA4C9A6D73@craigfrancis.co.uk>
References: <CAOfKkdRzoo7JuD07F8nkZBYvS5eDMiV2r6cNV-FgeLxBrdCsiQ@mail.gmail.com>
 <b8333cb6-eaa0-4170-a3ba-29eadb2fd8fa@www.fastmail.com>
 <CAOfKkdSWhQ5-wbnnWzb74VknGNVSM+2+5-sMoc-_yOEzk4JFFQ@mail.gmail.com>
 <CANS-=pdrGap4ep=14DL97xPDOdM0+6eQszy8JE0c8+c8v8rxdQ@mail.gmail.com>
To: Lynn <kjarli@gmail.com>
Subject: Re: [PHP-DEV] Discussion about new Curl URL API and ext/curl
 improvements
From: craig@craigfrancis.co.uk (Craig Francis)

On 17 Jun 2022, at 09:27, Lynn <kjarli@gmail.com> wrote:
> ... That said, we should avoid having: cURL procedural + cURL =
procedural in objects + cURL OOP. Having 2 different object based =
libraries to do the same thing PHP is confusing and will just end up in =
way too many Stack Overflow questions.
>=20
> Perhaps it is best to split this into 2 separate RFCs?




tbh, I'd worry the OOP version would need a fair amount of discussion, =
and experimentation... e.g. what the methods/parameters should be, =
deciding how errors/oddities are handled (where exceptions should be =
used, can NULL be returned (aka the 9.0 grenade), or other fancy =
approaches like monads?), and how `curl_multi_*` functionality would =
work.

Could the OOP work be done separately, maybe starting in userland, so =
those decisions could be made... and in the mean time, ext/curl gets a =
quick update to expose this new URL API in the procedural style (keeping =
consistency, and keeping it as a thin wrapper for now)?

Craig