envoyproxy/envoy

Make use of match tree in HCM route table

Open

#15.409 geöffnet am 10. März 2021

Auf GitHub ansehen
 (2 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)C++ (5.373 Forks)batch import
area/httparea/matchinghelp wanted

Repository-Metriken

Stars
 (27.997 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 8T) (378 gemergte PRs in 30 T)

Beschreibung

There's a few different ways of implementing this, but the most likely one seems to be to oneof it with the existing route table implementation. There are some challenges here due to existing couplings between the route table and filter APIs, e.g.

virtual Router::RouteConstSharedPtr route(const Router::RouteCallback& cb) PURE;

, but if we can skip supporting this for the new match tree this might be relatively easy.

One open question would be to see if we want to retain the idea of virtual hosts when using the match tree since we can express the :authority lookup within the match tree.

Contributor Guide