Awesome
<h1 align="center">http-service</h1> <div align="center"> <strong> Types and traits to help you implement your own HTTP server </strong> </div> <br /> <div align="center"> <!-- Crates version --> <a href="https://crates.io/crates/http-service"> <img src="https://img.shields.io/crates/v/http-service.svg?style=flat-square" alt="Crates.io version" /> </a> <!-- Downloads --> <a href="https://crates.io/crates/http-service"> <img src="https://img.shields.io/crates/d/http-service.svg?style=flat-square" alt="Download" /> </a> <!-- docs.rs docs --> <a href="https://docs.rs/http-service/"> <img src="https://img.shields.io/badge/docs-latest-blue.svg?style=flat-square" alt="docs.rs docs" /> </a> </div> <div align="center"> <h3> <a href="https://docs.rs/http-service/"> API Docs </a> <span> | </span> <a href="https://discordapp.com/channels/442252698964721669/474974025454452766"> Chat </a> </h3> </div>About
This crate has been deprecated. We recommend implementing inherent methods
such as Tide's
Server::respond
method instead.
The crate http-service provides the necessary types and traits to implement
your own HTTP Server.
For example you can use the workspace member
http-service-hyper to run an
HTTP Server.
- Runs via
http_service_hyper::run(HTTP_SERVICE, ADDRESS); - Returns a future which can be
awaited viahttp_service_hyper::serve(HTTP_SERVICE, ADDRESS);
Contributing
Want to join us? Check out our The "Contributing" section of the guide and take a look at some of these issues:
Conduct
The http-service project adheres to the Contributor Covenant Code of Conduct. This describes the minimum behavior expected from all contributors.
License
MIT OR Apache-2.0