- From: Watson Ladd <watsonbladd@gmail.com>
- Date: Sun, 5 Feb 2023 12:36:56 -0800
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Mark Nottingham <mnot@mnot.net>, Lucas Pardue <lucaspardue.24.7@gmail.com>, ietf-http-wg@w3.org
On Mon, Jan 23, 2023 at 10:48 PM Julian Reschke <julian.reschke@gmx.de> wrote: <snip much context> > > What I'm looking for is a strategy that avoid tons of flags in parsers, > and confusing APIs when using them. I'm a little confused by what you want. Is the situation the following: I put in a new kind of field for a new field My-Field. That new kind isn't understood by existing code, implementations that want My-Field to be parsed need to update their parser to parse the new kind. Because to me that's how everything should work. I'm not sure what the alternative is: how do we expect to parse fields whose grammer is not defined yet? Sincerely, Watson -- Astra mortemque praestare gradatim
Received on Sunday, 5 February 2023 20:37:24 UTC