package cdc_ft

Get desktop application:
View/edit binary Protocol Buffers messages

Send list of to-be-deleted files to the client.

• string directory = 1

  Files are relative to this directory.

• repeated string files = 2

  Files in |directory|.

• repeated string dirs = 3

  Directories in |directory|.

Send indices of missing and changed files to client.

• repeated uint32 client_indices = 1

  Client-side index of the file.

Send file list to server.

• string directory = 1

  Files are relative to this directory.

• repeated AddFilesRequest.File files = 2

  Files in |directory|.

• repeated string dirs = 3

  Directories in |directory|.

Used in: AddFilesRequest

• string filename = 1

• int64 modified_time = 2

  Linux epoch time. time_t, basically.

• uint64 size = 3

Send patching information to server. Uses SOA layout to save bandwidth. The arrays are expected to be of the same length.

• repeated AddPatchCommandsRequest.Source sources = 1

  Whether this is a reused chunk or a new chunk.

• repeated uint64 offsets = 2

  Offsets into |data| or the basis file, depending on the source.

• repeated uint32 sizes = 3

  Sizes in |data| or the basis file, depending on the source.

• bytes data = 4

  Data bytes, for SOURCE_DATA.

Used in: AddPatchCommandsRequest

• SOURCE_DATA = 0

  Use bytes [offset, offset + size) from |data| contained in this message. This means that no existing chunk can be reused.

• SOURCE_BASIS_FILE = 1

  Use bytes [offset, offset + size) from the basis file. This means that an existing chunk can be reused.

Send signatures for diffing file data to client. Uses SOA layout to save bandwidth. The arrays are expected to be of the same length.

• repeated uint32 sizes = 1

  Chunk sizes.

• bytes hashes = 2

  Chunk hashes, size should match (size of sizes) * (hash length).

Send stats to client for logging purposes.

• uint32 num_missing_files = 1

  Number of files present on the client, but not on the server.

• uint32 num_extraneous_files = 2

  Number of files present on the server, but not on the client.

• uint32 num_matching_files = 3

  Number of files present on both and matching.

• uint32 num_changed_files = 4

  Number of files present on both, but not matching.

• uint64 total_missing_bytes = 5

  Sum of the size of all missing files.

• uint64 total_changed_client_bytes = 6

  Sum of the client size of all changed files.

• uint64 total_changed_server_bytes = 7

  Sum of the server size of all changed files.

• uint32 num_missing_dirs = 8

  Number of directories present on the client, but not on the server.

• uint32 num_extraneous_dirs = 9

  Number of directories present on the server, but not on the client.

• uint32 num_matching_dirs = 10

  Number of directories present on both and matching.

Tell server that client will send data of a missing file.

• uint32 server_index = 1

  Server-side of the missing file.

Tell client that server is about to send signature data for diffing files.

• uint32 client_index = 1

  Client-side index of the file.

• uint64 server_file_size = 2

  The total size of the server-side file.

Send command line options to server. The options largely match the command line args.

• string destination = 1

• bool delete = 2

• bool recursive = 3

• int32 verbosity = 4

• bool whole_file = 5

• bool compress = 6

• repeated SetOptionsRequest.FilterRule filter_rules = 7

• bool checksum = 8

• bool relative = 9

• bool dry_run = 10

• bool existing = 11

• string copy_dest = 12

Used in: SetOptionsRequest

• FilterRule.Type type = 1

• string pattern = 2

Used in: FilterRule

• TYPE_INCLUDE = 0

• TYPE_EXCLUDE = 1

Tell server to shut the frick down.

(message has no fields)

Ack for ShutdownRequest.

(message has no fields)

Used for testing.

• string message = 1

Notify server that subsequent messages are going to be compressed, e.g. when the client is about to send missing files. Once all compressed data is sent, the client waits for the ToggleCompressionResponse.

(message has no fields)

Notify client that all compressed messages have been received (e.g. all missing files have been copied to the server) and that the client may switch to uncompressed transfer again. This "write fence" or "sync point" is necessary to prevent that the server reads past the compressed data because it doesn't know where compressed data ends.

(message has no fields)