package blimp.node.v0

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc Tunnel (stream TunnelMsg, stream TunnelMsg)

  controller.proto:11

• rpc ExposedTunnel (stream TunnelMsg, stream TunnelMsg)

  controller.proto:12

• rpc SyncNotifications (stream SyncStatusResponse, stream GetSyncStatusRequest)

  controller.proto:17

  The request and responses are flipped because the node controller is querying the CLI for status updates, but the CLI is initiating the connection.

  message SyncStatusResponse

  controller.proto:48

  • oneof msg

    • string old_token = 1

      Only used in handshake.

    • auth.v0.BlimpAuth auth = 3

    • bool synced = 2

  message GetSyncStatusRequest

  controller.proto:58

  (message has no fields)

Used in: TunnelMsg

(message has no fields)

Used in: TunnelMsg

• string token = 1

• string namespace = 2

Used in: TunnelMsg

• string name = 1

• uint32 port = 2

• string old_token = 3

• optional auth.v0.BlimpAuth auth = 5

The first message the Client sends to the server must be a header. After that all messages either direction must be bufs. Optionally, either direction may send an EOF to indicate they have no more to send.

Used as request type in: Controller.ExposedTunnel, Controller.Tunnel

Used as response type in: Controller.ExposedTunnel, Controller.Tunnel

• oneof msg

  • errors.v0.Error error = 1

  • TunnelHeader header = 2

  • ExposedTunnelHeader exposed_header = 5

  • bytes buf = 3

  • EOF eof = 4