Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support each route with different module #1205

Open
wolvever opened this issue Dec 10, 2024 · 0 comments
Open

Support each route with different module #1205

wolvever opened this issue Dec 10, 2024 · 0 comments

Comments

@wolvever
Copy link

Is your feature request related to a problem? Please describe.
By design there is no mapping between one route and set of modules. Thus all routes' traffic might go throught all modules. To avoid this each kind of module have to design a way to skip part of traffic.

The design has serveral disadvantage:

  • It's harder to figure out a http request goes through which modules.
  • A wrong matcher could result all traffic run through a not very good performance module, causing cluster level traffic jam.
  • Different module might have different way to config how to skip certain route / url path, making config harder to be right.

Describe the solution you'd like
Allow to config modules by route, each route may map to a sequence of modules. HandleAccept, HandleHandshake still use global modules.

Describe alternatives you've considered
None.

Additional context
None

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

No branches or pull requests

1 participant