envoyproxy/envoy
Voir sur GitHubSupport one-to-one mapping of upstream/downstream connections
Open
#12 370 ouverte le 29 juil. 2020
area/httpdesign proposalhelp wanted
Métriques du dépôt
- Stars
- (27 997 stars)
- Métriques de merge PR
- (Merge moyen 8j) (378 PRs mergées en 30 j)
Description
I’d like to have the ability to have exactly one upstream connection for every downstream connection that we decide to route. That is, streams on the same downstream connection should share the same upstream connection, but no other streams should use that upstream connection.
The rationale for this is twofold:
- I want to ensure that only the traffic for a single downstream client is carried over a given upstream connection. I do not want mixing of client traffic over an upstream connection. This would be solved by creating a new connection for every stream if it weren't for the second rationale
- I want to avoid the overhead of the TCP handshake that would be needed in the connection-per-stream case.
I have time to work on this feature if there is a consensus that it makes sense.