Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129489
Feedback-ID: ifab94697:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Mon, 01 Dec 2025 22:19:37 +0100
To: internals@lists.php.net
Message-ID: <ece6b228-7405-47be-93a4-663d7f014f43@app.fastmail.com>
In-Reply-To: 
 <CAH5C8xXUPKgd0wWwLC3G2Ye=kRZN58gK3DY82v5GoduBNNtb5A@mail.gmail.com>
References: 
 <CAH5C8xXUPKgd0wWwLC3G2Ye=kRZN58gK3DY82v5GoduBNNtb5A@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Followup Improvements for ext/uri
Content-Type: multipart/alternative;
 boundary=d53213a5c905478f8328b801de188019
From: rob@bottled.codes ("Rob Landers")

--d53213a5c905478f8328b801de188019
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Mon, Dec 1, 2025, at 21:50, M=C3=A1t=C3=A9 Kocsis wrote:
> Hi Everyone,
>=20
> I'd like to introduce my latest RFC that I've been working on for a wh=
ile now: https://wiki.php.net/rfc/uri_followup.
>=20
> It proposes 5 followup improvements for ext/uri in the following areas:
> - URI Building
> - Query Parameter Manipulation
> - Accessing Path Segments as an Array
> - Host Type Detection
> - URI Type Detection
> - Percent-Encoding and Decoding Support
>=20
> I did my best to write an RFC that was at least as extensive as https:=
//wiki.php.net/rfc/url_parsing_api had become by the end. Despite my eff=
orts,
> there are still a couple things which need a final decision, or which =
need to be polished/improved. Some examples:
>=20
> - How to support array/object values for constructing query strings? (=
https://wiki.php.net/rfc/uri_followup#type_support)
> - How to make the UriQueryParams and UrlQueryParams classes more inter=
operable with the query string component (mainly with respect to percent=
-encoding)? (https://wiki.php.net/rfc/uri_followup#percent-encoding_and_=
decoding)
> - Exactly how the advanced percent-decoding capabilities should work? =
Does it make sense to support all the possible modes (UriPercentEncoding=
Mode) for percent-decoding as well (https://wiki.php.net/rfc/uri_followu=
p#percent-encoding_and_decoding_support)
> - etc.
>=20
> Regards,
> M=C3=A1t=C3=A9

Hello!

For the builder methods, why not use the same wither method names? That =
would make switching to them really easy, over the current implementatio=
n.=20

=E2=80=94 Rob
--d53213a5c905478f8328b801de188019
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div><br></div><d=
iv><br></div><div>On Mon, Dec 1, 2025, at 21:50, M=C3=A1t=C3=A9 Kocsis w=
rote:</div><blockquote type=3D"cite" id=3D"qt" style=3D""><div dir=3D"lt=
r"><div>Hi Everyone,</div><div><br></div><div>I'd like to introduce my l=
atest RFC that I've been working on for a while now: <a href=3D"https://=
wiki.php.net/rfc/uri_followup">https://wiki.php.net/rfc/uri_followup</a>=
.</div><div><br></div><div>It proposes 5&nbsp;followup&nbsp;improvements=
 for ext/uri in the following areas:</div><div><div>- URI Building</div>=
<div>- Query Parameter Manipulation</div><div>- Accessing Path Segments =
as an Array</div><div>- Host Type Detection</div><div>- URI Type Detecti=
on</div><div>- Percent-Encoding and Decoding Support</div></div><div><br=
></div><div>I did my best to write an RFC that was at least as extensive=
 as&nbsp;<a href=3D"https://wiki.php.net/rfc/url_parsing_api">https://wi=
ki.php.net/rfc/url_parsing_api</a> had become by the end. Despite my eff=
orts,</div><div>there are still a couple things which need&nbsp;a final =
decision, or which need&nbsp;to be polished/improved. Some examples:</di=
v><div><br></div><div>- How to support array/object values for construct=
ing query strings? (<a href=3D"https://wiki.php.net/rfc/uri_followup#typ=
e_support">https://wiki.php.net/rfc/uri_followup#type_support</a>)</div>=
<div>- How to make the UriQueryParams and&nbsp;UrlQueryParams classes mo=
re interoperable with the query string component (mainly with respect to=
 percent-encoding)? (<a href=3D"https://wiki.php.net/rfc/uri_followup#pe=
rcent-encoding_and_decoding">https://wiki.php.net/rfc/uri_followup#perce=
nt-encoding_and_decoding</a>)</div><div>- Exactly how the advanced perce=
nt-decoding capabilities should work? Does it make sense to support all =
the possible modes (UriPercentEncodingMode) for percent-decoding as well=
 (<a href=3D"https://wiki.php.net/rfc/uri_followup#percent-encoding_and_=
decoding_support">https://wiki.php.net/rfc/uri_followup#percent-encoding=
_and_decoding_support</a>)</div><div>- etc.</div><div><br></div><div>Reg=
ards,</div><div>M=C3=A1t=C3=A9</div></div></blockquote><div><br></div><d=
iv>Hello!</div><div><br></div><div>For the builder methods, why not use =
the same wither method names? That would make switching to them really e=
asy, over the current implementation.&nbsp;</div><div><br></div><div id=3D=
"sig121229152">=E2=80=94 Rob</div></body></html>
--d53213a5c905478f8328b801de188019--