1c2d50680a
Noteworthy changes: - All constructors now follow the same pattern: `new` uses OS entropy, `from_rng` takes a `R: Rng` and seeds the randomness from there. `from_rng` is fallible, since randomness generators can be fallible. - `BalanceLayer` was renamed to `MakeBalanceLayer`, since it is not _really_ a `BalanceLayer`. The name of `BalanceMake` was also "normalized" to `MakeBalance`. Another observation: the `Debug` bound on `Load::Metric` in `p2c::Balance`, while not particularly onerous, generates really confusing errors if you forget it include it. And crucially, the error never points at `Debug` (should we file a compiler issue?), so I pretty much had to guess my way to that being wrong in the doc example. It would probably be useful to add a documentation example to `MakeBalanceLayer` or `MakeBalance` (I suspect just one of them is fine, since they're basically the same). Since I've never used it, and find it hard to think of uses for it, it might be good if someone with more experience with it wrote one.
Tower
Tower is a library of modular and reusable components for building robust networking clients and servers.
Overview
Tower aims to make it as easy as possible to build robust networking clients and servers. It is protocol agnostic, but is designed around a request / response pattern. If your protocol is entirely stream based, Tower may not be a good fit.
Project Layout
Tower consists of a number of components, each of which live in their own sub crates.
-
tower: The main user facing crate that provides batteries included tower services (docs). -
tower-service: The foundational traits upon which Tower is built (docs). -
tower-layer: The foundational trait to compose services together (docs). -
tower-balance: A load balancer. Load is balanced across a number of services (docs). -
tower-buffer: A buffering middleware. If the inner service is not ready to handle the next request,tower-bufferstores the request in an internal queue (docs). -
tower-discover: Service discovery abstraction (docs). -
tower-filter: Middleware that conditionally dispatch requests to the inner service based on a predicate (docs). -
tower-limit: Middleware limiting the number of requests that are processed (docs). -
tower-reconnect: Middleware that automatically reconnects the inner service when it becomes degraded (docs). -
tower-retry: Middleware that retries requests based on a givenPolicy(docs). -
tower-test: Testing utilies (docs). -
tower-timeout: Middleware that applies a timeout to requests (docs). -
tower-util: Miscellaneous additional utilities for Tower (docs).
Status
Currently, only tower-service, the foundational trait, has been released to
crates.io. The rest of the library will be following shortly.
License
This project is licensed under the MIT license.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tower by you, shall be licensed as MIT, without any additional terms or conditions.