Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124292
Precedence: bulk
MIME-Version: 1.0
References: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
In-Reply-To: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
Date: Mon, 8 Jul 2024 11:24:09 -0600
Message-ID: <CAM7F2--2W67u-awM-3QuDGqA6ojr4yAqAiaJ0dBxKxb65Hc2Rg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000003853e061cbfaf4c"
From: lnearwaju@gmail.com (Lanre)

--00000000000003853e061cbfaf4c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 28, 2024 at 3:38=E2=80=AFPM M=C3=A1t=C3=A9 Kocsis <kocsismate90=
@gmail.com> wrote:

> Hi Everyone,
>
> I've been working on a new RFC for a while now, and time has come to
> present it to a wider audience.
>
> Last year, I learnt that PHP doesn't have built-in support for parsing
> URLs according to any well established standards (RFC 1738 or the WHATWG
> URL living standard), since the parse_url() function is optimized for
> performance instead of correctness.
>
> In order to improve compatibility with external tools consuming URLs (lik=
e
> browsers), my new RFC would add a WHATWG compliant URL parser functionali=
ty
> to the standard library. The API itself is not final by any means, the RF=
C
> only represents how I imagined it first.
>
> You can find the RFC at the following link:
> https://wiki.php.net/rfc/url_parsing_api
>
> Regards,
> M=C3=A1t=C3=A9
>
>
I was exploring wrapping ada_url for PHP (
https://github.com/lnear-dev/ada-url). It works, but it's a bit slower,
likely due to the implementation of the objects. I was planning to embed
the zvals directly in the object, similar to PhpToken, but I haven't had
the chance and don't really need it anymore. Shouldn't be too much work to
clean it up though

--00000000000003853e061cbfaf4c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, Jun 28, 2024 at 3:38=E2=80=AFPM M=
=C3=A1t=C3=A9 Kocsis &lt;<a href=3D"mailto:kocsismate90@gmail.com" target=
=3D"_blank">kocsismate90@gmail.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Everyone,<div><br></d=
iv><div>I&#39;ve been working on a new RFC for a while now, and time has co=
me to present it to a wider audience.</div><div><br></div><div>Last year, I=
 learnt that PHP doesn&#39;t have built-in support for parsing URLs accordi=
ng to any well established=C2=A0standards (RFC=C2=A01738 or the WHATWG URL =
living standard), since the parse_url() function is optimized for performan=
ce instead of correctness.</div><div><br></div><div>In order to improve com=
patibility with external tools consuming=C2=A0URLs (like browsers), my new =
RFC would add a WHATWG compliant URL parser functionality to the standard l=
ibrary. The API itself is not final by any means, the RFC only represents h=
ow I imagined it first.</div><div><br></div><div>You can find the RFC at th=
e following link:=C2=A0<a href=3D"https://wiki.php.net/rfc/url_parsing_api"=
 target=3D"_blank">https://wiki.php.net/rfc/url_parsing_api</a></div><div><=
br></div><div>Regards,</div><div>M=C3=A1t=C3=A9</div><div><br></div></div><=
/blockquote><div><br></div><div>I was exploring wrapping <code>ada_url</cod=
e> for PHP (<a rel=3D"noreferrer" href=3D"https://github.com/lnear-dev/ada-=
url">https://github.com/lnear-dev/ada-url</a>). It works, but it&#39;s a bi=
t slower, likely due to the implementation of the objects. I was planning t=
o embed the zvals directly in the object, similar to <code>PhpToken</code>,=
 but I haven&#39;t had the chance and don&#39;t really need it anymore. Sho=
uldn&#39;t be too much work to clean it up though=C2=A0<br></div></div>
</div>

--00000000000003853e061cbfaf4c--