Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-02-23 Thread Tim Düsterhus
Hi [dropping Dennis from the Cc list] Am 2025-02-21 13:06, schrieb Tim Düsterhus: We already had extensive off-list discussion about the RFC and I agree it's in a good shape now. I've given it another read and here's my remarks: One more thing that came to my mind, but where I'm not sure wha

RE: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-02-23 Thread Juris Evertovskis
-Original Message- From: Tim Düsterhus Sent: Sunday, February 23, 2025 5:05 PM To: Máté Kocsis Cc: Internals Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API > Naming of `WhatWgError` and `WhatWgErrorType`. They are placed within the `Uri\WhatWg` namespace

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-02-23 Thread Paul M. Jones
Hi all, In earlier discussions on the [Server-Side Request and Response objects](https://externals.io/message/108436) RFC and the [after-action sumamry](https://externals.io/message/109563), one of the common non-technical objections was that it would better be handled in userland. Seeing as t

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-02-23 Thread Gina P. Banyard
Hi Máté, I've read the latest version of the RFC and while I very much like the RFC, I have some remarks. 1. The paragraph in at the beginning of the RFC in the > Relevant URI specifications > WHATWG URL section seems to be incomplete. 2. I don't really understand how the UninitializedUriExcep

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-02-23 Thread Gina P. Banyard
On Sunday, 23 February 2025 at 17:57, Paul M. Jones wrote: > Hi all, > > In earlier discussions on the Server-Side Request and Response objects RFC > and the after-action sumamry, one of the common non-technical objections was > that it would better be handled in userland. > > Seeing as there