Better routing #8

New Issue

Jef Roosens · 2024-02-08T15:36:36+01:00

Jef Roosens commented

2024-02-08 15:36:36 +01:00

Regex isn't the best solution for matching routes, as it's rather cpu intensive. Instead, I'd like to implement parametrized routes using a trie-like structure, which would hopefully be much faster than the current methods.

This would support the usual expected stuff, /:var for matching a single keyword, or /*var for matching multiple segments.

Together with this, I'd like to introduce "routers", structs that allow defining multiple grouped routes which can then all be mapped to the same subpath on the main router, eg putting all /api routes into a single router.

To do

Literal string matching
Single-segment wildcard matching
Output wildcard segment matches
Replace old router with new one
Add API functions for retrieving matched segments

Regex isn't the best solution for matching routes, as it's rather cpu intensive. Instead, I'd like to implement parametrized routes using a trie-like structure, which would hopefully be much faster than the current methods. This would support the usual expected stuff, `/:var` for matching a single keyword, or `/*var` for matching multiple segments. Together with this, I'd like to introduce "routers", structs that allow defining multiple grouped routes which can then all be mapped to the same subpath on the main router, eg putting all `/api` routes into a single router. ## To do - [x] Literal string matching - [x] Single-segment wildcard matching - [x] Output wildcard segment matches - [ ] Replace old router with new one - [x] Add API functions for retrieving matched segments

Jef Roosens added the

enhancement

label 2024-02-08 15:36:36 +01:00

Jef Roosens added reference routing

2024-02-22 18:20:44 +01:00

Jef Roosens commented

2024-02-22 19:47:46 +01:00

Poster

For the API for accessing matched variables, we should introduce a trie for matching the variable names so they can be referenced using their names.

Jef Roosens closed this issue

2024-03-02 22:38:07 +01:00

Sign in to join this conversation.