trillium VS tower-http

i like trillium a lot. inspired by plug (elixir), you just add plugs in a vertical stack and the request goes from top to bottom. there is also ntex which has a ton of examples inspired by actix-web (might have been a fork) https://github.com/ntex-rs/examples

Maybe you want something like this, which is a Cow-like enum that either holds a &mut T or a T?

I've been planning on using trillium on a project, the main difference I can see between it and Axum is that Axum allows you to use existing tower middle ware, right?

I'll definitely prioritize this! I hadn't really thought much about it because it's straightforward to do in application code, but it seems reasonable to make it easier for people to get started with this common use case. I opened up a discussion on gh, let me know if something like what you had in mind https://github.com/trillium-rs/trillium/discussions/36

Any thoughts on (trillium)[https://github.com/trillium-rs/trillium]? Looks like you're fulfilling similar niches.

If your goal is specifically a web proxy, you also might want to take a look at async Rust such as hyper and tower-http, which are part of the tokio ecosystem. (But spawning threads could be just fine too, if it's not super performance-sensitive.)

here's the issue for more detailed info: https://github.com/tower-rs/tower-http/issues/136

tower-http has several simple middleware if you're looking for more examples. AddExtension, SetRequestHeader and SetResponseHeader are good places to start. If you want to see something that goes all-in then Trace is probably the most complex middleware in tower-http.

You could also look at https://github.com/tower-rs/tower-http which is a work in progress set of HTTP specific middlewares for tower. It also has examples that uses hyper as the HTTP server.