Crate reactive_messaging

Modules

SocketClient
The handle to define, start and shutdown a Reactive Client for Socket Connections BUFFERED_MESSAGES_PER_PEER_COUNT is the number of messages that may be produced ahead of sending (to the server) as well as the number of messages that this client may accumulate from the server before denying new ones
SocketServer
The handle to define, start and shutdown a Reactive Server for Socket Connections.
BUFFERED_MESSAGES_PER_PEER_COUNT is the number of messages that may be produced ahead of sending (to each client) as well as the number of messages that this server may accumulate from each client before denying new ones

ReactiveMessagingDeserializer
Trait that should be implemented by enums that model the “remote messages” to be consumed by a “Responsive Processor” – “remote messages” may either be messages produced by the remote server or by the remote client (when we are implementing the opposite peer).
This trait, therefore, specifies how to deserialize() enum variants received by the remote peer (like RON, for textual protocols)
ReactiveMessagingSerializer
Trait that should be implemented by enums that model the “local messages” to be sent to the remote peer – “local messages” may either be messages generated by the server or by the client, depending on if you’re building a server or client.
This trait, therefore, specifies how to:
ResponsiveMessages
Adherents will, typically, also implement [ReactiveMessagingUnresponsiveSerializer].
By upgrading your type with this trait, it is possible to build a “Responsive Processor”, where the returned Stream contains the messages to be sent as an answer to the remote peer.
This trait, therefore, specifies (to the internal sender) how to handle special response cases, like “no answer” and “disconnection” messages.