immerrr again

@euri10 the low priority thing is understandable. i asked it in the PR, but let me reiterate, is there anything that would help to get the ball rolling here? i...

ref #773, ref #527, ref #389

@euri10 is there anything i can do to help get this in? or at least to help to get the discussion started, as i would assume there's a decision to...

Heyy, now we're talking (literally), thanks! I'll update the PR to use the extensions approach, or if you see another way to store the start/end timestamps within the scope of...

@euri10 i have updated the code to use `scope['extensions']['uvicorn_request_duration']` to store the timestamps, but like i said previously, if there's a better place to put it, just let me know.

I agree with the concerns listed above, as i mentioned earlier, it was done the way it was done to minimize the scope of change and to let the uvicorn...

Not sure if i understand the last question correctly, but i think the format is available as `self.log.cfg.access_log_format` On the following line: https://github.com/encode/uvicorn/pull/947/files#diff-7c8a9d71c98f0ed83c32a88a1b7e777ef85776c98869045d24c74e3f7714494aR41 And I am making use of it...

It can be made to work. It's been a while since I wrote this, but i think the default uvicorn logging uses colours, whereas gunicorn doesn't support that, so we...

Just started implementing the requested changes, and ran into another point of contention/agreement. The existing uvicorn logging is done when response is started, whereas gunicorn logging is done when the...

~~Oh, and another thing that should work right now and will not with the new suggested approach is the handling of gunicorn's `--access-logfile`. Current implementation takes the pre-configured logger object...