Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118185
MIME-Version: 1.0
References: <CAOfKkdR0cab4-rWdVpzGPtg8nraNBWLN3whe9xs2mAw5x1MVyw@mail.gmail.com>
In-Reply-To: <CAOfKkdR0cab4-rWdVpzGPtg8nraNBWLN3whe9xs2mAw5x1MVyw@mail.gmail.com>
Date: Mon, 4 Jul 2022 19:37:15 -0400
Message-ID: <CAOfKkdTg3Fi1LHojGXGREEaxy9CpkB6rn4qwh0AQr6Nv4kof_w@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ecba3705e3033781"
Subject: Re: [RFC][Vote] New Curl URL API
From: pierrick@php.net (Pierrick Charron)

--000000000000ecba3705e3033781
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Sorry, I forgot to include the RFC Url :
https://wiki.php.net/rfc/curl-url-api

Le lun. 4 juill. 2022, =C3=A0 19 h 34, Pierrick Charron <pierrick@php.net> =
a
=C3=A9crit :

> 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 featur=
e
> 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
>

--000000000000ecba3705e3033781--