Lines Matching full:middleware

32 //! middleware with [`Service`]s. If a [`Service`] can be thought of as an
35 //! different type. The [`ServiceBuilder`] type is used to add middleware to a
52 //! middleware, and [utilities] for working with [`Service`]s and [`Layer`]s.
59 //! middleware. This means that the `tower` crate on its own does *not* provide
62 //! application code, libraries providing middleware implementations, and
70 //!   the middleware [provided by this crate](#modules) and by other libraries
73 //! * **Implementing middleware** to add custom behavior to network clients and
74 //!   servers in a reusable manner. This might be general-purpose middleware
75 //!   (and if it is, please consider releasing your middleware as a library for
82 //!   allowing users to add arbitrary Tower middleware to those clients.
86 //!   provided by existing Tower middleware, a protocol implementation might use
87 //!   Tower middleware internally, as well as as an integration point.
122 //! The various middleware implementations provided by this crate are feature
124 //! default, all the optional middleware are disabled.
126 //! To get started using all of Tower's optional middleware, add this to your
134 //! only the [`retry`] and [`timeout`][timeouts] middleware, write:
140 //! See [here](#modules) for a complete list of all middleware provided by