async-std-hyper
warp
async-std-hyper | warp | |
---|---|---|
1 | 66 | |
40 | 9,140 | |
- | - | |
0.0 | 6.3 | |
over 1 year ago | 25 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
async-std-hyper
-
Tokio, the async runtime for Rust, hits 1.0
Here is an example: https://github.com/async-rs/async-std-hyper/blob/master/READ...
You do have to write a ~50 loc compat layer. However, most of the compat layer is due to the fact that tokio's `AsyncRead` and `AsyncWrite` are different from the standard futures crate, which may change in the future [0]. After that, you just have to implement `hyper::Executor` for async-std's `spawn`, and `hyper::Accept` for async-std's `TcpListener`.
Of course, it is not as generic as `Future`, but it is relatively simple. As @steveklabnik mentioned:
> There's a few points here that still need some interop work. The intention is to fix that, but it's non-trivial. We'll get there.
[0]: https://github.com/tokio-rs/tokio/issues/2716
warp
-
Hyper – A fast and correct HTTP implementation for Rust
I tried warp [0] and I am unimpressed so far. Pretty complex, limited documentation, buggy. The builder paradigm they used feels pretty constrained and, in my opinion, achieve the opposite of the simplicity it is supposed to bring. I was surprised it is so popular.
Maybe I need more time or a favorable comparison to another framework to appreciate it.
[0] https://github.com/seanmonstar/warp
-
How in hell can Warp be considered "super easy"?
Have you gone through the (examples)[https://github.com/seanmonstar/warp/blob/master/examples/]? There's actually a lot of explicit instructions here on how to use Warp, and all of them are very straightforward to read (e.g., (this example with route parameters and a POST'ed body)[https://github.com/seanmonstar/warp/blob/master/examples/body.rs])
-
Custom Warp error messages
There are numerous guides how to do custom error messages using the routes .recover() method (including the official one ), but it seems quite inflexible since I can't (seem to?) pass the actual error messages back to user.
-
Rendering a Rust project's file dependency tree in the terminal
$ brew install gabotechs/taps/dep-tree $ git clone https://github.com/seanmonstar/warp $ dep-tree render warp/src/lib.rs lib.rs◁─────────────┬────────────────────────────────┬──────┬┐ │ │ │ ││ ├▷filter/and.rs◁────────────────────────────┐ │ ││ ├▷│filter/map_err.rs◁───────────────────────┤ │ ││ ├▷││filter/or.rs◁───────────────────────────┤ │ ││ ├▷│││filters/mod.rs◁─────────────┬──────┬───────────────────┼┤ ├▷││││test.rs───────┘ │ │ │ │ ││ │ │││││ │ │ │ │ ││ │ │││├│▷filters/addr.rs │ │ │ │ ││ │ │││├│▷│filters/any.rs │ │ │ │ ││ │ │││├│▷││filters/body.rs │ │ │ │ ││ │ │││├│▷│││filters/compression.rs│ │ │ │ ││ │ │││├│▷││││filters/cookie.rs────┘ │ │ │ ││ │ │││├│▷│││││filters/cors.rs │ │ │ ││ │ │││├│▷││││││filters/ext.rs │ │ │ ││ │ │││├│▷│││││││filters/fs.rs │ │ │ ││ │ │││├│▷││││││││filters/header.rs │ │ │ ││ │ │││├│▷│││││││││filters/host.rs │ │ │ ││ │ │││├│▷││││││││││filters/log.rs │ │ │ ││ │ │││├│▷│││││││││││filters/method.rs │ │ │ ││ │ │││├│▷││││││││││││filters/multipart.rs│ │ │ ││ │ │││├│▷│││││││││││││filters/path.rs────┤ │ │ ││ │ │││├│▷││││││││││││││filters/query.rs │ │ │ ││ │ │││├│▷│││││││││││││││filters/reply.rs │ │ │ ││ │ │││├│▷││││││││││││││││filters/sse.rs──┘ │ │ ││ │ │││├│▷│││││││││││││││││filters/trace.rs │ │ ││ │ │││││ ││││││││││││││││││ │ │ ││ ├─────────────────────────▷filter/boxed.rs◁─┤ │ ││ ├─────────────────────────▷│filter/map.rs◁──┤ │ ││ ├─────────────────────────▷││filter/wrap.rs◁┼───────────────┼─┐ │ │││││ ││││││││││││││││││ │││ │ │ │││ ├─────────────────────────────▷filter/mod.rs◁──────┬┬┼───────┤│ │ │││││ ││││││││││││││││ ││ │ │││ │││ │ │││││ ││││││││││││││││ ││ ├▷filter/and_then.rs┤││ │││ │ │││││ ││││││││││││││││ ││ ├▷│filter/or_else.rs┘││ │││ │ │││││ ││││││││││││││││ ││ ├▷││filter/recover.rs┘│ │││ ├───────────────────────────────▷│││filter/service.rs◁──────┼─┤ │ │││││ ││││││││││││││││ ││ ├▷││││filter/then.rs──┤ │││ │ │││││ ││││││││││││││││ ││ ├▷│││││filter/unify.rs┘ │││ │ │││││ ││││││││││││││││ ││ ├▷││││││filter/untuple_one.rs┤││ │ │││││ ││││││││││││││││ ││ │ │││││││ │││ ├───────────────────────────────────────▷reply.rs◁───┬──────────┐ ├───────────────────────────────────────▷│route.rs───│──────┤││ │ │ │││││ ││││││││││││││││ ││ │ │││││││ │ │ │││ │ ├──────────────────────────────────────────▷server.rs◁────────┤ │ │ │││││ ││││││││││││││││ ││ │ │││││││ │ │ │ │││ │ ├────────────────────────────────────────────▷tls.rs─┴──────┘││ │ │ │││││ ││││││││││││││││ ││ │ │││││││ │ │ │ ││ │ ├──────────────────────────────────────────────▷filters/ws.rs◁│ │ ├──────────────────────────────────────────────▷│transport.rs││ │ │ │││ │ ││││││││││││││││ ││ │ │││││││ │ │ │ │ ││ │ ├─────────────────────────────────────────────────▷generic.rs││ │ ├─────────────────────────────────────────────────▷reject.rs─┴┘ │ │ │ │ │ │ ├───────────────────────────────────────────────────▷error.rs │ └───────────────────────────────────────────────────▷redirect.rs┘
-
Is there a more practical way to let warp respond to incoming requests?
What I see on the examples for the warp crate is that the examples do this:
-
I turned The Rust Book into a crate
You might want to consider using Alacritty instead of Warp. Warp is VC-funded, macOS only, closed source, and it phones home. They also kinda stole the name of a web framework.
-
I made rust-webapp-template
warp server,
-
Help with warp routes
Hello, I'd need some help with warp routes since I'm not familiar with the framework. If somebody knows how to do this I'd appreciate very much.
-
Any Rust based forum software?
If one were to undertake a project of developing something like this, which is the best web framework for it. I did some cursory research and discovered these back-end frameworks - actix, axum, poem, salvo, warp, gotham and rocket.
-
shuttle v0.7.1 has been released (improved isolation, new supported frameworks, QOL improvements)
We've added support for the warp, salvo & thruster frameworks
What are some alternatives?
reqwest - An easy and powerful Rust HTTP Client
axum - Ergonomic and modular web framework built with Tokio, Tower, and Hyper
async-std - Async version of the Rust standard library
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
smol - A small and fast async runtime for Rust
Rocket - A web framework for Rust.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
hyper - An HTTP library for Rust
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
hyperterm - A terminal built on web technologies
stylus - Lightweight status page for home infrastructure
kitty - Cross-platform, fast, feature-rich, GPU based terminal