warp: a web framework for Rusthttp://seanmonstar.com/post/176530511587/warp …
-
-
Replying to @seanmonstar
This is incredibly exciting; the cleanest, easiest Rust web framework I've tried so far. Filters make perfect sense. Building simple applications with warp feels *right*.
2 replies 1 retweet 9 likes -
Replying to @josh_triplett
Thanks! That's fast! ;D let me know what feels off or doesn't work (I never write bugs!)
3 replies 0 retweets 0 likes -
Replying to @seanmonstar
How hard would it be to extract fixed string components from a set of filters and create a faster route dispatcher that doesn't do a bunch of individual string comparisons? (Almost certainly not the bottleneck, but still, curious how feasible that'd be with this routing.)
1 reply 0 retweets 1 like -
Replying to @josh_triplett
If I keep the Filter trait sealed, I think I can add a method to determine the full path matched by a filter chain, and could use that with a router. That said, with filters you can build a tree naturally, preventing matching the prefix over and over.
1 reply 0 retweets 1 like -
Replying to @seanmonstar
I'm not just talking about a common prefix; I'm talking about having a huge branching factor, with numerous endpoints. Matching a large number of strings in parallel can be done much more efficiently than a series of 1:1 comparisons.
1 reply 0 retweets 1 like
Indeed. In that case, I think it can work with the format I mentioned. @carllerche had this exact question, and it's probably solvable.
I think it'll also be solvable manually by adding a path filter where the user matches however they'd like.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.