HTTP dynamic path segments #19
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The code is functional and works, marked it WIP for discussion.
Inspired by #18, I implemented HTTP path arguments into
FuyuServer
.Implementation differs from @nexus4880's version by not using LINQ and using multi-threading for lookup to offset the cost of segment matching.
Discussion
I'm not happy with setting
path
insideFuyuBehaviour
's constructor. Suggestions and ideas are welcome!Since
FuyuServer
contains a unique identifier (FuyuServer.Name
), maybe we can bindFuyuBehaviour
on runtime toFuyuServer
by using a new attribute[FuyuRoute(string serverName, string path)]
and initialize FuyuBehaviour using it?