Expand description
Rivven Wire Protocol
This crate defines the wire protocol types shared between rivven-client and rivvend. It provides serialization/deserialization for all protocol messages.
§Protocol Stability
The enum variant order is significant for postcard serialization. Changes to variant order will break wire compatibility with existing clients/servers.
§Example
ⓘ
use rivven_protocol::{Request, Response};
// Serialize a request
let request = Request::Ping;
let bytes = request.to_bytes()?;
// Deserialize a response
let response = Response::from_bytes(&bytes)?;Structs§
- Broker
Info - Broker/node information for metadata discovery
- Delete
Records Result - Delete records result for a partition
- Message
Data - Serialized message data for transport
- Partition
Metadata - Partition metadata for cluster discovery
- Quota
Alteration - Quota alteration request
- Quota
Entry - Quota entry in describe response
- Topic
Config Description - Topic configuration in describe response
- Topic
Config Entry - Topic configuration entry for AlterTopicConfig
- Topic
Config Value - Topic configuration value with metadata
- Topic
Metadata - Topic metadata for cluster discovery
Enums§
- Protocol
Error - Protocol error types
- Request
- Protocol request messages
- Response
- Protocol response messages
Constants§
- MAX_
MESSAGE_ SIZE - Maximum message size (64 MiB)
- PROTOCOL_
VERSION - Protocol version for compatibility checking
Type Aliases§
- Result
- Result type for protocol operations