Lines Matching full:middleware

43 middleware with [`Service`]s. If a [`Service`] can be thought of as an
46 different type. The [`ServiceBuilder`] type is used to add middleware to a
63 middleware, and [utilities] for working with [`Service`]s and [`Layer`]s.
70 middleware. This means that the `tower` crate on its own does *not* provide
73 application code, libraries providing middleware implementations, and
81   the middleware [provided by this crate][all_layers] and by other libraries
84 * **Implementing middleware** to add custom behavior to network clients and
85   servers in a reusable manner. This might be general-purpose middleware
86   (and if it is, please consider releasing your middleware as a library for
93   allowing users to add arbitrary Tower middleware to those clients.
97   provided by existing Tower middleware, a protocol implementation might use
98   Tower middleware internally, as well as as an integration point.
139 The various middleware implementations provided by this crate are feature
141 default, all the optional middleware are disabled.
143 To get started using all of Tower's optional middleware, add this to your
151 only the [`retry`] and [`timeout`][timeouts] middleware, write:
157 See [here][all_layers] for a complete list of all middleware provided by