Module networking 

Types for configuring network channels with serialization formats, transports, etc.

Structs

EmbeddedTransport

Items cross a channel that the host of an embedded program implements however it likes (a network connection, an in-memory queue, …), keeping the guarantees of the policy F.

NetworkingConfig

A network channel configuration with T as transport backend and S as the serialization backend.

Tcp

Send items across a length-delimited TCP channel.

Udp

Send items across a UDP channel, which does not guarantee delivery or ordering.

Enums

Bincode

Serialize items using the bincode crate.

Embedded

Leaves serialization of items to code outside of Hydro. Every EMBEDDED channel uses it.

FailStop

A TCP failure policy that stops sending messages after a failed connection.

Lossy

A failure policy that allows messages to be lost.

LossyDelayedForever

A failure policy that treats dropped messages as indefinitely delayed.

NetworkingInfo

Describes the networking configuration for a network channel at the IR level.

NoSer

An unconfigured serialization backend.

TcpFault

The fault model for a TCP connection.

UdpFault

The fault model for a UDP channel.

Constants

EMBEDDED

A network channel implemented by the host of an embedded program, which chooses how messages travel: a network connection, an in-memory queue, or anything else that delivers them with the guarantees of the chosen failure policy (for example EMBEDDED.fail_stop().name("messages")).

TCP

A network channel that uses length-delimited TCP for transport.

UDP

A network channel that uses UDP for transport.

Traits

NetworkFor

A networking backend implementation that supports items of type T.

TcpFailPolicy

A failure policy for TCP connections, determining how the transport handles connection failures and what ordering guarantees the output stream provides.

TransportKind

A transport backend for network channels.

UdpFailPolicy

A failure policy for UDP channels, determining how the transport handles message loss. Because UDP provides no ordering guarantees, all policies produce NoOrder output streams, and there is no fail_stop option (UDP is connectionless, so there is no connection to fail).