package d2m

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message BeginTransaction

md-d2m.proto:252

Acquires a device group lock for an atomic operation shared across the device group. Reflection messages from the device to the mediator server will only be reflected once the transaction is committed. Type: 0x40 Direction: Client --> Server

message BeginTransactionAck

md-d2m.proto:268

Acknowledges that the device group lock has been acquired and that the transaction has been started. Type: 0x41 Direction: Client <-- Server

(message has no fields)

message ClientHello

md-d2m.proto:80

Initial message from the client, containing the authentication challenge response and additional login information. Type: 0x11 Direction: Client --> Server

enum ClientHello.DeviceSlotsExhaustedPolicy

md-d2m.proto:104

Policy to be applied in case the device id is not registered on the server and all device slots have been exhausted.

Used in: ClientHello

message ClientUrlInfo

md-d2m.proto:29

Send along client information when connecting to the mediator server. This message is serialized, hex-encoded (lowercase) and then used as the WebSocket path. Type: n/a Direction: Client -> Server

message CommitTransaction

md-d2m.proto:274

Commits a transaction, releases a device group lock. Type: 0x42 Direction: Client --> Server

(message has no fields)

message CommitTransactionAck

md-d2m.proto:281

Acknowledges that the transaction has been committed and that the device group lock has been released. Type: 0x43 Direction: Client <-- Server

(message has no fields)

enum DeviceSlotExpirationPolicy

md-d2m.proto:56

Policy determining the device slot's lifetime.

Used in: ClientHello, DevicesInfo.AugmentedDeviceInfo

enum DeviceSlotState

md-d2m.proto:66

Device registration state on the mediator server.

Used in: ClientHello, ServerInfo

message DevicesInfo

md-d2m.proto:190

Device information of all devices. Type: 0x31 Direction: Client <-- Server

message DevicesInfo.AugmentedDeviceInfo

md-d2m.proto:192

Device id to (augmented) device info map of all devices.

Used in: DevicesInfo

message DropDevice

md-d2m.proto:217

Request to drop a device and free its device slot. Type: 0x32 Direction: Client --> Server

message DropDeviceAck

md-d2m.proto:227

Acknowledges that a device has been dropped and the device slot has been free'd. Type: 0x33 Direction: Client <-- Server

message GetDevicesInfo

md-d2m.proto:184

Request device information of all devices. Type: 0x30 Direction: Client --> Server

(message has no fields)

enum ProtocolVersion

md-d2m.proto:17

D2M protocol versions.

message ReflectionQueueDry

md-d2m.proto:169

The device's reflection queue on the server has been fully transmitted to the device. Note: This does not mean that reflected messages have already been acknowledged by the device! Type: 0x20 Direction: Client <-- Server

(message has no fields)

message RolePromotedToLeader

md-d2m.proto:176

The device's role has been promoted to leader, indicating that the device should now request to receive and reflect messages from the chat server. Type: 0x21 Direction: Client <-- Server

(message has no fields)

message ServerHello

md-d2m.proto:44

Initial message from the server, containing an authentication challenge. Type: 0x10 Direction: Client <-- Server

message ServerInfo

md-d2m.proto:131

Parts of the server's configuration and the device slot state. Type: 0x12 Direction: Client <-- Server

message SetSharedDeviceData

md-d2m.proto:236

Set the shared device data which is being sent to each device during login. Type: 0x34 Direction: Client --> Server

message TransactionEnded

md-d2m.proto:307

When a transaction ends (either because it was committed or because the device disconnected), this message is sent to all connected devices except for the device that committed the transaction. This can be used by the other devices as a "retry signal" if a previous "BeginTransaction" attempt was unsuccessful. Type: 0x45 Direction: Client <-- Server

message TransactionRejected

md-d2m.proto:288

A `BeginTransaction` request is rejected because another transaction is already in process. Type: 0x44 Direction: Client <-- Server