| Commit message (Collapse) | Author | Age | Files |
| |
|
| |
|
|
|
|
|
|
|
| |
Introduce a new protocol InitProtocol which can be used as the core protocol
for initializing a connection with a peer.
Move the handshake logic from the PeerPool module to the protocols directory and
build a handshake protocol that implements InitProtocol trait.
|
|
|
|
| |
connection handling
|
| |
|
|
|
|
| |
internal proc macros
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
new tasks
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
bounded channels
Remove all unbounded channels to prevent unbounded memory usage and
potential crashes.
Use `FuturesUnordered` for sending to multiple channels simultaneously.
This prevents the sending loop from blocking if one channel is blocked,
and helps handle errors properly.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
`ServerBuilder` and `ClientBuilder`
|
| |
|
| |
|
|
|
|
|
|
| |
Add a limit for receiving notifications for the subscription. If this
limit is exceeded, the client will stop and raise an error. The limit is
configurable when building a new client.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
clean up examples
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|