tower/Cargo.toml

[workspace]

members = [
  "tower",
  "tower-balance",
  "tower-buffer",
  "tower-discover",
  "tower-filter",
  "tower-hedge",
  "tower-layer",
  "tower-limit",
  "tower-load-shed",
  "tower-reconnect",
  "tower-retry",
  "tower-service",
  "tower-test",
  "tower-timeout",
  "tower-util",
]
Add middleware 2017-10-03 10:03:14 -07:00			`[workspace]`

			`members = [`
Create subdir for tower crate (#182) 2019-03-06 07:54:39 -08:00			`"tower",`
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",`
Add hedge retry middleware (#236) Add tower-hedge, a layer that preemptively retries requests which have been outstanding for longer than a given latency percentile. If either of the original future or the retry future completes, that value is used. For more information about hedge requests, see: [The Tail at Scale][1] [1]: https://cseweb.ucsd.edu/~gmporter/classes/fa17/cse124/post/schedule/p74-dean.pdf Signed-off-by: Alex Leong <alex@buoyant.io> 2019-04-27 09:32:26 -07:00			`"tower-hedge",`
layer: Add `tower-layer` and the `Layer` trait (#163) This change introduces the new `tower-layer` crate and the foundational `Layer` trait to go along with it. This trait allows one to easily compose a set of `Service`s that take an inner service. These services only modify the request/response. This also provides the `Layer` implementation for many of the tower crates. 2019-02-27 12:28:42 -08:00			`"tower-layer",`
Consolidate `limit` layers (#235) * Consolidate `limit` layers - `InFlightLimit` and `RateLimit` are moved into `tower-limit` crate. - `InFlightLimit` is renamed to `ConcurrencyLimit`. Fixes #225 2019-04-05 20:08:43 -07:00			`"tower-limit",`
Introduce tower-load-shed (#204) Provides a middleware that immediately fails any request if the underlying service isn't ready yet. This is useful when used in conjunction with `InFlightLimit` or others, so that requests are rejected immediately, instead of keeping track of extra pending requests. 2019-03-20 15:48:10 -07:00			`"tower-load-shed",`
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",`
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",`
Create `tower-test` and include tower-mock. (#237) tower-mock is deleted in favor of having a single test crate. This crate also includes a new macro: `assert_request_eq!`. 2019-04-07 20:42:18 -07:00			`"tower-test",`
Add middleware 2017-10-03 10:03:14 -07:00			`"tower-timeout",`
util: rename tower-service-util -> tower-util (#212) 2019-03-27 16:34:56 -07:00			`"tower-util",`
Add middleware 2017-10-03 10:03:14 -07:00			`]`