package basis.core.transport.proto

Get desktop application:
View/edit binary Protocol Buffers messages

• oneof PossibleMessages

  • TransportManagerInfo transport_manager_info = 2

    string error = 1;

  • MessageSchemas schemas = 3

  • RequestSchemas request_schemas = 4

• oneof PossibleMessages

  • string error = 1

  • NetworkInfo network_info = 2

  • MessageSchemas schemas = 3

Used in: MessageSchemas

• string serializer = 1

• string name = 2

• string schema = 3

• string hash_id = 4

• bytes schema_efficient = 5

Used in: ClientToCoordinatorMessage, CoordinatorMessage

• repeated MessageSchema schemas = 1

// todo not implemented on either side message PublishersDelta { map<string, RepeatedPublisherInfo> added_publishers = 1; map<string, RepeatedPublisherInfo> removed_publishers = 2; }

Used in: CoordinatorMessage

• map<string, RepeatedPublisherInfo> publishers_by_topic = 1

Used in: RepeatedPublisherInfo, TransportManagerInfo

• uint64 publisher_id_high = 1

• uint64 publisher_id_low = 2

• string topic = 3

  TODO: type TODO: this results in a lot of duplication of topic names, but its probably ok - topic names are mostly unique

• string schema_id = 4

• map<string, string> transport_info = 5

Coordinator -> TransportManager

Used in: NetworkInfo

• repeated PublisherInfo publishers = 1

Used in: ClientToCoordinatorMessage

• repeated string schema_ids = 1

• int64 nsecs = 1

  The current simulated time

• uint64 run_token = 2

  Changes every time a replay or simulation starts

TransportManager -> Coordinator

Used in: ClientToCoordinatorMessage

• repeated PublisherInfo publishers = 1

  todo we should consider letting these also be mapped, to simplify things