ClientSession inside an aiohttp Server does not support connection pooling

[alexmac]

I've got a aiohttp server that makes multiple http requests to other services in response to its inbound requests, I want to use a ClientSession for each inbound request to handle any cookie state that may be needed across the downstream requests it makes - but this means my server makes no use of connection-pooling/keep-alive when making downstream requests.

I could share a single ClientSession across all inbound requests, but then cookie/header state within the ClientSession would be re-used across inbound requests, which would not be correct. I could perhaps create a SharedClientSession object that handled switching between cookies/headers with a single underlying ClientSession, but that seems like I'm fighting the system.

Is there a supported way to do this? The most elegant way I can imagine would be a single ClientSession per inbound request with a global tcpconnector - except the ClientSession takes ownership and closes it, making it impossible to use in this way.

[fafhrd91]

client session accepts connector_owner parameter.

@asvetlov seems we need to document connector_owner parameter.

[asvetlov]

Hmmm. Maybe. Not only mention the param in reference but provide usage example.
Sorry, I'm at EuroPython and have very limited free time.

[alexmac]

My bad for not reading the code, glad it's implemented the way I wanted! But some doc improvements would be nice

[asvetlov]

Keep open until doc update.

[asvetlov]

See also #2067

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.