Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122379
Mailing-List: contact internals-help@lists.php.net; run by mlmmj
Precedence: bulk
MIME-Version: 1.0
References: <CAESVnVp11-EVBrhzSj16=Nd3fYE366piq6fG-9wV3+iH8TxchA@mail.gmail.com>
In-Reply-To: <CAESVnVp11-EVBrhzSj16=Nd3fYE366piq6fG-9wV3+iH8TxchA@mail.gmail.com>
	=?UTF-8?B?Yg==?= <6562680@gmail.com>
Date: Thu, 15 Feb 2024 10:38:45 +0300
Message-ID: <CAK=iT=WaoTWJjnTA0QE9AfOVKCpytrVPcx68KLDn3JBC_q2ixw@mail.gmail.com>
Subject: Re: [RFC] OOP API for cURL extension
To: Sara Golemon <pollita@php.net>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000c08219061166b9ba"
From: 6562680@gmail.com (=?UTF-8?B?0JPRgNC40LPQvtGA0LjQuSBTZW5pb3IgUEhQIC8g0KDQsNC30YDQsNCx0L7RgtGH0LjQuiBXZQ==?==?UTF-8?B?Yg==?=)

--000000000000c08219061166b9ba
Content-Type: text/plain; charset="UTF-8"

Working with remote servers is a little bit harder than just catching the
exception.

Just implement OOP stuff gives no benefit except "do not read the docs, but
use IDE". Usually count of curl options is so big that it wont help.

And also, there's multicurl too.
There's batch calling with limit too.
There's errors of different types. I mean curl errors on create, curl
errors on execute, http errors (network), response errors (invalid data,
misformatted data), and api errors, that could be sent even with 200 code.

How try/catch will solve? Easy solution, too many discussion points.

--000000000000c08219061166b9ba
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:verdana,sans-serif">Working with remote servers is a little bit ha=
rder than just catching the exception.</div></div><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr"><div class=3D"gmail_default" style=
=3D"font-family:verdana,sans-serif"><br>Just implement OOP stuff gives no b=
enefit except &quot;do not read the docs, but use IDE&quot;. Usually count =
of curl options is so big that it wont help.<br><br>And also, there&#39;s m=
ulticurl too.<br>There&#39;s batch calling with limit too.<br>There&#39;s e=
rrors of different types. I mean curl errors on create, curl errors on exec=
ute, http errors (network), response errors (invalid data, misformatted dat=
a), and api errors, that could be sent even with 200 code.<br><br>How try/c=
atch will solve? Easy solution, too many discussion points.</div><br></div>=
</div><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"></div></d=
iv></div>

--000000000000c08219061166b9ba--