Uses old Rust 2015
|0.2.4||Sep 7, 2018|
|0.2.3||Jul 25, 2018|
|0.1.8||Jun 6, 2018|
|0.1.7||May 23, 2018|
|0.1.2||Mar 28, 2018|
#161 in HTTP server
35 downloads per month
An Asynchronous, Extensible, Micro web framework for Rust.
Asynchronous. In arc reactor, Service Handlers are asynchronous by default.
Integration With futures-await. The
#[service]proc_macro not only derives the
ArcServicetrait for your route handler, but also marks it as
#[async]so you can await on futures in your route handlers with no extra stress.
Intuitive Middleware System. arc reactor exposes a middleware system that is easy to reason about. Have a look at the design spec
Minimalistic. arc reactor is designed to be a very thin abstraction over tokio and hyper.
TLS Support. easy to add tls support.
Opt-in to Nightly. arc reactor uses a lot of cool features, including
proc_macroswhich are only available on the nightly channel, using the
Add this to your
arc-reactor = "0.2"
Originally, arc-reactor was designed for the nightly compiler.
But instabilities in
libprocmacro cause it to break everytime a new nightly compiler is released.
So by default, arc-reactor no longer uses the nightly compiler, and will work out of the box with the stable compiler. 🎉
This means experimental nightly features including proc_macros are only available behind the
unstable feature flag.
If you wish to use arc-reactor, with the nightly compiler and unstable feature enabled:
It is recommended that you lock down the compiler version. Until
libprocmacro is stablized.
If you wish to use arc-reactor with it's default features:
- The trait
ArcServiceis implemented for all functions that satisfy the signature
Fn(Request, Response) -> FutureResponse
- The trait
MiddleWare<Request>is implemented for all functions that satisfy the signature
Fn(Request) -> MiddleWareFuture<Request>
- The trait
MiddleWare<Response>is implemented for all functions that satisfy the signature
Fn(Response) -> MiddleWareFuture<Response>
futures-rsis re-exported instead of
- you lose the ability to
await!on futures in your ServiceHandlers and MiddleWares.
- Currently, Multipart support is implemented using unstable features, so you would have to implement your own.
Check out the examples folder and the api documentation to get a feel for how
arc reactor works.
It's well documented and should get you up and running in no time.
It is Strongly recommended that you read the design document, as it gives you full disclosure on arc-reactor's internals, as well as the design decisions that were made.
Arc-Reactor is highly extensible via middlewares which are placed in the
Some of the things are missing include:
- Support byte range headers
- Asynchronous StaticFileServer
- Json body parser
- Multipart Support
Feel free to submit a PR.
Refer to License.