Re: [httpapi] Structured Fields for HTTP APIs

[Julian Reschke <[e-mail]>]

On 14.02.2023 11:27, Erik Wilde wrote:
> ...
>> How do these products cope with things like HTTP/2 and HTTP/3? Let me
>> guess: either they don't, or they leverage libs and/or operating
>> systems. If they can do that for that, why not for field value parsing?
>
> it's the former, mostly. and that's why backward-compatibility is such
> an important consideration. designs were based on the assumption that
> simple parsing machinery (think regex) is good enough.

Well - it never was.

>> I struggle to see the alternative. How do these tools *currently* parse
>> things like Content-Type, Accept, Prefer, or Cache-Control?
>
> sometimes specific parsers, sometimes simple generic machinery mostly
> based on some regex variant.
>
>> Are there *any* tools in this space which are open source? If so, do
>> they support SF? If they do not, have change requests been submitted?
>> (Pointers?)
>
> yes there are open source tools and that's an interesting question. i
> don't know, to be honest, but i'll try to find out. my guess is that
> since so far there's little demand to parse SF in the wild and lots of
> demand to implement new features, that's where the focus will be. but
> i'll try to find out.
> ...

Very much appreciated!

Best regards, Julian