Skip to content

Commit cadb3b1

Browse files
Add a short explanation for "pipeline" in tutorial "Channel" chapter (#823)
1 parent 72a28e5 commit cadb3b1

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

content/tokio/tutorial/channels.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,9 @@ means that exclusive access is required to call it. We could open a connection
6666
per task, but that is not ideal. We cannot use `std::sync::Mutex` as `.await`
6767
would need to be called with the lock held. We could use `tokio::sync::Mutex`,
6868
but that would only allow a single in-flight request. If the client implements
69-
[pipelining], an async mutex results in underutilizing the connection.
69+
[pipelining] (in short, sending many commands without waiting for each prior
70+
command's response), an async mutex results in underutilizing
71+
the connection.
7072

7173
[pipelining]: https://redis.io/topics/pipelining
7274

0 commit comments

Comments
 (0)