36 releases (breaking)

0.26.2 May 1, 2024
0.26.1 Dec 9, 2023
0.26.0 Nov 5, 2023
0.25.0 Jun 20, 2023
0.1.1 Jul 13, 2020

#1546 in Network programming

Download history 44498/week @ 2024-02-03 46762/week @ 2024-02-10 56907/week @ 2024-02-17 49721/week @ 2024-02-24 46393/week @ 2024-03-02 46482/week @ 2024-03-09 49795/week @ 2024-03-16 48142/week @ 2024-03-23 63268/week @ 2024-03-30 59619/week @ 2024-04-06 52211/week @ 2024-04-13 47477/week @ 2024-04-20 40030/week @ 2024-04-27 38848/week @ 2024-05-04 45551/week @ 2024-05-11 34513/week @ 2024-05-18

165,297 downloads per month
Used in 196 crates (6 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
~222K SLoC