Andrew Godwin

I don't think it is totally necessary - I just lifted it from WSGI, presuming they had a reason for it, but I don't think it's been very useful in...

There are reference docs as you linked, but they're specification-style and not particularly user friendly; a shorter page with more human explanations and maybe a diagram would probably help. (and...

Yes, this is not for _incoming_ request headers, but for _outgoing_ request headers. I agree that all incoming ones should be lowercased; it's the response headers that it seems we...

There's also a point where we can't accommodate literally every single HTTP feature - ASGI has always been about handling 98% of cases, not 100%. I might argue that proxying...

At the time the spec was designed, we did an extensive review of a lot of different backends, applications and servers in the Python ecosystem and beyond, and header case...

I considered adding them into the spec when I was writing it, but as you say, the user agent support is very spotty. ASGI in general is meant to be...

@pgjones If gRPC uses them as that issue suggests, then that would make me think there's some value in adding support.

Trailers are a really, really gnarly part of the HTTP spec, though. I resisted adding them to ASGI for all this time as they're something 99% of applications won't need,...

Yes, the use of them by GRPC is probably enough of a reason at this point - trust those folks to go resurrect a dusty old part of the HTTP...

The irony of pooling a threadpool is not lost on me, but if it provides significant enough performance benefits, maybe it's worth it. Any idea what % saving this is...