- From: Mark Nottingham <notifications@github.com>
- Date: Tue, 19 Dec 2023 17:51:08 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/url/issues/577/1863719372@github.com>
@thx1111: > Then, by "exceptional circumstance", you meant modifying, literally, the document BCP35 itself, and not the resulting list of registered "schemes" referencing BCP35? I stand corrected. Understand that RFC 8820 is best current practice for applications that use HTTP (what some people call "HTTP APIs" or "REST APIs") -- it's saying that it's exceptional that a one of them would require a new scheme. > Still, there is the problem of modifying existing, or creating new, applications able to utilize any particular scheme. I don't expect that my web browser actually supports the currently 374 different registered schemes available. In fact, the trend has been for, for instance, web browsers to drop support for less commonly used schemes - no more gopher, ftp, or mailto - with some functionality being replaced by specialized scheme applications or by "groupware" suites. Browsers are going to have to change if they want to support anything that happens here, so that isn't a decisive factor regarding syntax. > I still don't agree that defining and registering a new scheme, exclusively to support html rendering from a local unix domain socket, is a good idea. HTTP isn't just for HTML. To be clear, I don't think a new scheme is the only way to do this; it's just more straightforward than other suggestions so far. @agowa: > You already have seen my initial suggestion in another ticket? > https://github.com/whatwg/url/issues/778#issue-1796979425 I hadn't, but that seems like a _lot_ of work (and abstraction) to get to the goals here. Normally, protocols can negotiate transitions like this (see eg the evolution from HTTP 1-3). What's different here is that unix domain sockets have a completely different authority, **and** a subtly different transport (as opposed to TCP). -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/577#issuecomment-1863719372 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/577/1863719372@github.com>
Received on Wednesday, 20 December 2023 01:51:14 UTC