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
Copy file name to clipboardExpand all lines: protocol/README.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,14 @@ A BIP324 library to establish and communicate over an encrypted channel.
4
4
5
5
The library is designed with a bare `no_std` and "Sans I/O" interface to keep it as agnostic as possible to application runtimes, but higher level interfaces are exposed for ease of use.
6
6
7
-
The `futures` feature includes the high-level `AsyncProcotol` type which helps create and manage an encrypted channel.
7
+
The `tokio` feature includes the high-level `AsyncProcotol` type which helps create and manage an encrypted channel.
8
8
9
9
The lower-level `CipherSession` and `Handshake` types can be directly used by applications which require more control. The handshake performs the one-and-a-half round trip dance between the peers in order to generate secret materials and verify a channel. A successful handshake results in a cipher session which performs the encrypt and decrypt operations for the lifetime of the channel.
10
10
11
11
## Feature Flags
12
12
13
13
*`std` -- Standard library dependencies for I/O, memory allocation, and random number generators.
14
-
*`futures` -- High level wrappers for asynchronous read and write runtimes using agnostic futures-rs traits.
15
-
*`tokio` -- Same wrappers as `futures`, but using the popular tokio runtime's specific traits instead of futures-rs.
14
+
*`tokio` -- High level I/O wrappers for asynchronous tokio runtime.
0 commit comments