Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118189
MIME-Version: 1.0
References: <CAOfKkdR0cab4-rWdVpzGPtg8nraNBWLN3whe9xs2mAw5x1MVyw@mail.gmail.com>
In-Reply-To: <CAOfKkdR0cab4-rWdVpzGPtg8nraNBWLN3whe9xs2mAw5x1MVyw@mail.gmail.com>
Date: Tue, 5 Jul 2022 09:13:45 +0200
Message-ID: <CADyq6sKhdHNO1ruPZK=BKghG-N+y77byuvf9yV1+kV9114MBiQ@mail.gmail.com>
To: Pierrick Charron <pierrick@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000091d86305e3099831"
Subject: Re: [PHP-DEV] [RFC][Vote] New Curl URL API
From: ocramius@gmail.com (Marco Pivetta)

--00000000000091d86305e3099831
Content-Type: text/plain; charset="UTF-8"

Clear "no" from me on this: this is something similar to a PSR-7 URI
object, but with a clunky and mutable API.

Something like this would/should go to packagist first, to assess adoption
there, but I would certainly not use it.

On Tue, 5 Jul 2022, 01:34 Pierrick Charron, <pierrick@php.net> wrote:

> Hi internals,
>
> I opened voting for the new Curl URL API as part of PHP8.2.
>
> All recent discussions show that we are not even close to getting a
> consensus on how the new CurlUrl OO API should be done. After changing my
> mind 300 times in the last day, I decided to only propose the procedural
> implementation that stays consistent with other functions of the ext/curl
> to target 8.2. I know this is not the ideal scenario, but with 8.2 feature
> freeze in two weeks, this is I think the only approach that will not put us
> in a potentially bad/harmful situation for a better future with ext/curl.
>
> The vote will last for 2 weeks and end on 19th of July.
>
> Regards
> Pierrick
>

--00000000000091d86305e3099831--