zecfoundation
/
tower
mirror of https://github.com/ZcashFoundation/tower.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
tower/Cargo.toml

26 lines
449 B
TOML
Raw Normal View History

Add middleware
2017-10-03 10:03:14 -07:00
[workspace]
members = [
Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
"tower-balance",
Initial buffer sketch (#13)
2017-10-10 10:38:40 -07:00
"tower-buffer",
Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
"tower-discover",
Add middleware
2017-10-03 10:03:14 -07:00
"tower-filter",
InFlightLimit middleware (#49) Provides a middleware that sets a maximum number of requests that can be in-flight for the service. A request is defined to be in-flight from the time `call` is invoked to the time the returned response future resolves. This maximum is enforced across all clones of the service instance.
2018-02-20 11:04:03 -08:00
"tower-in-flight-limit",
Add middleware
2017-10-03 10:03:14 -07:00
"tower-mock",
"tower-rate-limit",
Initial discovery, balance, and reconnect sketchs (#12)
2017-10-05 13:41:44 -07:00
"tower-reconnect",
Tower Retry (#96) - Inspect the request, response, and error when determining to retry - Return a future if retry is desired - This future allows an impl to delay a retry - The future yields a new `Policy`, allowing state to be changed for later retries.
2018-08-28 11:05:15 -07:00
"tower-retry",
Rename `tower-route` -> `tower-router`. (#26) `Route` as a verb is easily confused with the noun.
2017-11-02 12:26:32 -07:00
"tower-router",
Extract `Service` trait and related into crate. (#67) This makes the `tower` crate available to be a "batteries included" facade.
2018-04-25 12:35:52 -07:00
"tower-service",
Add middleware
2017-10-03 10:03:14 -07:00
"tower-timeout",
Add tower-util (#19) * NewServiceFn * OptionService * EitherService
2017-10-21 14:06:39 -07:00
"tower-util",
Introduce tower-watch (#87) `tower_watch::WatchService` provides a dynamically-bound `Service` that updates in response to a `Watch`. A `WatchService` is constructed with a `Watch<T>` and a `Bind<T>` -- `Bind` is a newly introduced trait that supports instantiating new service instances with a borrowed value, i.e. from a watch. This can be used to reconfigure Services from a shared or otherwise externally-controlled configuration source (for instance, a file system).
2018-07-11 15:03:20 -07:00
"tower-watch",
Add middleware
2017-10-03 10:03:14 -07:00
]
Add backpresure capabilities to `Service` (#6) Currently, `Service` does not provide a mechanism by which it can signal to the caller that it is at capacity. This commit adds a `poll_ready` function to the `Service` trait. Callers are able to first check `poll_ready` before calling `Service::call`. `poll_ready` is expected to be a hint and will be implemented in a best effort fashion. It is permitted for a `Service` to return `Ready` from `poll_ready` and the next invocation of `Service::call` fails.
2017-09-27 10:40:02 -07:00
[dev-dependencies]
Extract `Service` trait and related into crate. (#67) This makes the `tower` crate available to be a "batteries included" facade.
2018-04-25 12:35:52 -07:00
futures = "0.1"
Upgrade to env_logger 0.5 and log 0.4 so that projects that use those (#52) versions don't have to build both those versions and the older ones that h2 is currently using. Don't enable the regex support in env_logger. Applications that want the regex support can enable it themselves; this will happen automatically when they add their env_logger dependency. Disable the env_logger dependency in quickcheck. The result of this is that there are fewer dependencies. For example, regex and its dependencies are no longer required at all, as can be seen by observing the changes to the Cargo.lock. That said, env_logger 0.5 does add more dependencies itself; however it seems applications are going to use env_logger 0.5 anyway so this is still a net gain. Submitted on behalf of Buoyant, Inc. Signed-off-by: Brian Smith <brian@briansmith.org>
2018-02-23 20:24:22 -08:00
log = "0.4.1"
env_logger = { version = "0.5.3", default-features = false }
Add backpresure capabilities to `Service` (#6) Currently, `Service` does not provide a mechanism by which it can signal to the caller that it is at capacity. This commit adds a `poll_ready` function to the `Service` trait. Callers are able to first check `poll_ready` before calling `Service::call`. `poll_ready` is expected to be a hint and will be implemented in a best effort fashion. It is permitted for a `Service` to return `Ready` from `poll_ready` and the next invocation of `Service::call` fails.
2017-09-27 10:40:02 -07:00
tokio-timer = "0.1"
futures-cpupool = "0.1"