-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Sub router #154
Comments
Unlike Gorilla's router, there's no performance gain from using subrouting, because the trie algorithm already handles this inherently. So the question becomes one of how to construct formulaic paths. Although it would be a nice-to-have feature, my approach to this has been to wrap a *Router within my own path builder code instead. |
I'm less interested in performance than being able to unify routes based on a common path. I know how well this library performs already :) |
See #89 |
Remove requirement of Service Mesh in Knative Signed-off-by: Michael Gasch <[email protected]>
My two cents: one reason subrouters would be useful is for applying some middleware to only a subrouter. For instance, I'd like to adapt this |
这是来自QQ邮箱的假期自动回复邮件。
您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。
|
I searched through the issues but couldn't find anything for sub routers with paths. I don't care about subdomains.
My use case is for API versioning. Here is a snippet from the Gorilla mux:
It would be sweet to have a sub router for each version prefix. Is this currently possible or something you could add?
Forgive me if I missed something in the README or documentation.
The text was updated successfully, but these errors were encountered: