Enhance connection pooling - Githubissues

akamai / hface

Hackable HTTP/{1,2,3} {client,server,proxy}

https://hface.readthedocs.io

Apache License 2.0

30 stars 3 forks source link

Enhance connection pooling #12

Open mila opened 1 year ago

mila commented 1 year ago

hface client maintains pools of connections to different hosts, but I am not sure that the pooling properly handles app possible. circumstances:

Open up to 6 (configurable) parallel connections to each origin for HTTP/1
Try to keep HTTP/1.1 connection alive but respect Connection: close
Handle HTTP/1.0 responses without Content-Length
Respect MAX_CONCURRENT_STREAMS for HTTP/2 and MAX_STREAMS for HTTP/3
Handle the unlikely situation that we run out of stream IDs.
Handle connections closed gracefully, TCP EOF, or broken streams
Handle GOAWAY
Reopen connection after various error.
Make sure that streams and connections are closed properly.
Handle timeouts from a peer.
Consider timeouts from our side.

mila commented 1 year ago

HTTPProtocol implementations have is_available() and has_expired() methods. I am not sure that this is the best API. If we use methods like this, we should make sure that they reflect events consumed from next_event(), not just buffered based on received data.