Re: [RFC] OOP API for cURL extension
| From: | Григорий Senior PHP / Разработчик We b | Date: | Thu, 15 Feb 2024 07:38:45 +0000 |
| Subject: | Re: [RFC] OOP API for cURL extension | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-122379@lists.php.net to get a copy of this message | ||
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.