Recently, updates landed in Envoy related to connection pooling, which moved the old implementations into Envoy::Http::Legacy.
We are currently still referring to classes from Envoy::Http::Legacy for our own connection pool implementations. It would be good to evaluate a course of action to move over to the new pool implementations. Possibly we can purge some of our own experimental code for h2/multiple connection support.
Recently, updates landed in Envoy related to connection pooling, which moved the old implementations into
Envoy::Http::Legacy.We are currently still referring to classes from
Envoy::Http::Legacyfor our own connection pool implementations. It would be good to evaluate a course of action to move over to the new pool implementations. Possibly we can purge some of our own experimental code for h2/multiple connection support.