Skip to content

http2: moving functionality from http2 pool to client#13869

Merged
alyssawilk merged 1 commit intoenvoyproxy:masterfrom
alyssawilk:http2_changes
Nov 3, 2020
Merged

http2: moving functionality from http2 pool to client#13869
alyssawilk merged 1 commit intoenvoyproxy:masterfrom
alyssawilk:http2_changes

Conversation

@alyssawilk
Copy link
Contributor

As part of #3431 we need to move the logic from HTTP/1 and HTTP/2 connection pools to the active client, so the new mixed connection pool can just create an active client of the right type and have all the logic in the client, not split between the client and the pool.

This removes functions for the HTTP/2 pool not moved in #13867

Risk Level: Medium (data plane refactor)
Testing: existing tests pass
Docs Changes: n/a
Release Notes: n/a
Part of #3431

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@alyssawilk
Copy link
Contributor Author

(CI is fine except for CodeQL)

@alyssawilk alyssawilk merged commit 6cb7419 into envoyproxy:master Nov 3, 2020
@alyssawilk alyssawilk deleted the http2_changes branch June 10, 2021 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants