39 releases (breaking)

0.28.0 Jan 14, 2025
0.27.0 Aug 9, 2024
0.26.3 Jun 4, 2024
0.26.1 Dec 9, 2023
0.1.1 Jul 13, 2020

#1718 in Network programming

Download history 60137/week @ 2025-01-31 68426/week @ 2025-02-07 71295/week @ 2025-02-14 63581/week @ 2025-02-21 64818/week @ 2025-02-28 65004/week @ 2025-03-07 63118/week @ 2025-03-14 65209/week @ 2025-03-21 62203/week @ 2025-03-28 69451/week @ 2025-04-04 57912/week @ 2025-04-11 57976/week @ 2025-04-18 70112/week @ 2025-04-25 57256/week @ 2025-05-02 59856/week @ 2025-05-09 56022/week @ 2025-05-16

255,920 downloads per month
Used in 268 crates (7 directly)

MIT license

1MB
16K SLoC

Generic request/response protocols.

General Usage

The Behaviour struct is a NetworkBehaviour that implements a generic request/response protocol or protocol family, whereby each request is sent over a new substream on a connection. Behaviour is generic over the actual messages being sent, which are defined in terms of a Codec. Creating a request/response protocol thus amounts to providing an implementation of this trait which can then be given to Behaviour::with_codec. Further configuration options are available via the Config.

Requests are sent using Behaviour::send_request and the responses received as Message::Response via Event::Message.

Responses are sent using Behaviour::send_response upon receiving a Message::Request via Event::Message.

Predefined codecs

In case your message types implement serde::Serialize and serde::Deserialize, you can use two predefined behaviours:

Protocol Families

A single Behaviour instance can be used with an entire protocol family that share the same request and response types. For that purpose, Codec::Protocol is typically instantiated with a sum type.

Limited Protocol Support

It is possible to only support inbound or outbound requests for a particular protocol. This is achieved by instantiating Behaviour with protocols using ProtocolSupport::Inbound or ProtocolSupport::Outbound. Any subset of protocols of a protocol family can be configured in this way. Such protocols will not be advertised during inbound respectively outbound protocol negotiation on the substreams.

Dependencies

~8–16MB
~195K SLoC