You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 25, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,6 +101,17 @@ check out some of the original Tower [guides].
101
101
We work exactly the same as Tower, expect in an async manner and slightly easier to use as such.
102
102
But the core ideas are obviously the same, so it should never the less help you to get started.
103
103
104
+
Browse the examples at [`tower-async-http/examples`](https://github.com/plabayo/tower-async/tree/master/tower-async-http/examples) to see some examples
105
+
on how to use `tower-async` and its sibling crates. While these are focussed on http examples,
106
+
note that:
107
+
108
+
- `tower-async` can work for any request-response flow (akin to `tower`);
109
+
- you can also use `tower-async` with http web services without making use of the `tower-async-http` crate,
110
+
it only is there to provide extra middleware for http-specific purposes, but this is all optional.
111
+
112
+
The documentation also contains some smaller examples and of course the codebase can be read as well,
113
+
together with its unit tests.
114
+
104
115
## Sponsorship
105
116
106
117
Regular and onetime sponsors alike help us to pay the development and service costs
@@ -181,8 +192,8 @@ We do not have a roadmap for Tower Async. But here are some ideas on what you ca
Copy file name to clipboardExpand all lines: tower-async/README.md
+16-5Lines changed: 16 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,7 +116,7 @@ with this (Aync Trait) version (Fork).
116
116
117
117
## Usage
118
118
119
-
Tower provides an abstraction layer, and generic implementations of various
119
+
Tower (Async) provides an abstraction layer, and generic implementations of various
120
120
middleware. This means that the `tower-async` crate on its own does *not* provide
121
121
a working implementation of a network client or server. Instead, Tower's
122
122
[`Service` trait][`Service`] provides an integration point between
@@ -170,19 +170,30 @@ To get started using all of Tower's optional middleware, add this to your
170
170
`Cargo.toml`:
171
171
172
172
```toml
173
-
tower-async = { version = "0.4", features = ["full"] }
173
+
tower-async = { version = "0.1", features = ["full"] }
174
174
```
175
175
176
176
Alternatively, you can only enable some features. For example, to enable
177
177
only the [`timeout`][timeouts] middleware, write:
178
178
179
179
```toml
180
-
tower-async = { version = "0.4", features = ["timeout"] }
180
+
tower-async = { version = "0.1", features = ["timeout"] }
181
181
```
182
182
183
183
See [here][all_layers] for a complete list of all middleware provided by
184
184
Tower.
185
185
186
+
Browse the examples at [`tower-async-http/examples`](https://github.com/plabayo/tower-async/tree/master/tower-async-http/examples) to see some examples
187
+
on how to use `tower-async` and its sibling crates. While these are focussed on http examples,
188
+
note that:
189
+
190
+
- `tower-async` can work for any request-response flow (akin to `tower`);
191
+
- you can also use `tower-async` with http web services without making use of the `tower-async-http` crate,
192
+
it only is there to provide extra middleware for http-specific purposes, but this is all optional.
193
+
194
+
The documentation also contains some smaller examples and of course the codebase can be read as well,
Copy file name to clipboardExpand all lines: tower-async/src/lib.rs
+15-4Lines changed: 15 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -158,18 +158,29 @@
158
158
//! `Cargo.toml`:
159
159
//!
160
160
//! ```toml
161
-
//! tower-async = { version = "0.4", features = ["full"] }
161
+
//! tower-async = { version = "0.1", features = ["full"] }
162
162
//! ```
163
163
//!
164
164
//! Alternatively, you can only enable some features. For example,
165
165
//! to enable only the [`timeout`][timeouts] middleware, write:
166
166
//!
167
167
//! ```toml
168
-
//! tower-async = { version = "0.4", features = ["timeout"] }
168
+
//! tower-async = { version = "0.1", features = ["timeout"] }
169
169
//! ```
170
170
//!
171
171
//! See [here][all_layers] for a complete list of all middleware provided by
172
172
//! Tower.
173
+
//!
174
+
//! Browse the examples at [`tower-async-http/examples`](https://github.com/plabayo/tower-async/tree/master/tower-async-http/examples) to see some examples
175
+
//! on how to use `tower-async` and its sibling crates. While these are focussed on http examples,
176
+
//! note that:
177
+
//!
178
+
//! - `tower-async` can work for any request-response flow (akin to `tower`);
179
+
//! - you can also use `tower-async` with http web services without making use of the `tower-async-http` crate,
180
+
//! it only is there to provide extra middleware for http-specific purposes, but this is all optional.
181
+
//!
182
+
//! The documentation also contains some smaller examples and of course the codebase can be read as well,
0 commit comments