Get desktop application:
View/edit binary Protocol Buffers messages
General namespace arguments
Used in:
In single chain/non-clustered environment, use namespace=""
Fail the operation if our preferred file name is not available
Used in:
If OK, then chunk_pos is defined.
Used in:
,Used in:
,TODO: not implemented yet
Must match with machi.hrl's values!
Used in:
Used in:
Used in:
For data type rationale, see comments for machi_flu1_client:checksum_list/4 or http://basho.github.io/machi/edoc/machi_flu1_client.html#checksum_list-4
Used in:
, , ,TODO: must be required, in future?
chunk_csum() type
Used in:
, ,chunk_pos() type
Used in:
, , , , , ,Used in:
,Used in:
,epoch_id() type
Used in:
, , , , , , , ,Error response - may be generated for any Req
Used in:
,Free-form (depends on server, which is probably a bad idea TODO)
file_info() type
Used in:
,Used in:
, , , , , , , , , , , , , , , , , , , ,* There is no timout error code, only PARTITION. If the client * wants to know if a lot of time has elapsed, then the client * can do its own timekeeping.
The whole file was trimmed
Only for testing by the Taipan
Used in:
General namespace arguments
Fail the operation if our preferred file name is not available
Used in:
If OK, then chunk_pos is defined.
Used in:
Used in:
For data type rationale, see comments for machi_flu1_client:checksum_list/4 or http://basho.github.io/machi/edoc/machi_flu1_client.html#checksum_list-4
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
(message has no fields)
Used in:
Used in:
Used in:
Used in:
Used in:
General namespace arguments
Use flag_no_checksum=non-zero to skip returning the chunk's checksum. TODO: not implemented yet.
Use flag_no_chunk=non-zero to skip returning the chunk (which only makes sense if flag_checksum is not set). TODO: not implemented yet.
Used in:
Used in:
Used in:
Used in:
Used in:
TODO: If we wish to support pipelined requests sometime in the future, this is the placeholder to do it.
CLIENTS must not set 'do_not_alter' flag; leave it to default.
The client should only define one request message. If the client includes multiple requests here, the server may pick/choose an arbitrary one. NOTE: The erlang protobuffs compiler doesn't support 'oneof'. But 'oneof' appears to be a very tiny memory optimization that not all languages might care about? (Erlang doesn't)
Re-use from high level API
Re-use from high level API
TODO: If we wish to support pipelined requests sometime in the future, this is the placeholder to do it.
Generic error response, typically used when something quite bad/unexpected happened within the server. Clients should always check this response and, if defined, ignore any request-specific response at codes 10+.
Specific responses.
Re-use from high level API
Re-use from high level API
No reponse to Mpb_LL_KickProjectionReactionReq = 18;
Used in:
General namespace arguments
Used in:
Used in:
Used in:
No options
Used in:
(message has no fields)
Used in:
Used in:
General namespace arguments
Used in:
Used in:
Used in:
TODO: Add flag for file glob/regexp/other filter type TODO: What else could go wrong?
Used in:
(message has no fields)
Used in:
Wow, I cannot use optional & repeated together?
Used in:
Used in:
Used in:
#p_srvr{} type
Used in:
Used in:
, , , , ,Used in:
, , ,No namespace arguments are required because NS is embedded inside of the file name.
Used in:
Use flag_no_checksum=non-zero to skip returning the chunk's checksum. TODO: not implemented yet.
Use flag_no_chunk=non-zero to skip returning the chunk (which only makes sense if flag_no_checksum is not set). TODO: not implemented yet.
TODO: not implemented yet.
Used in:
TODO: If we wish to support pipelined requests sometime in the future, this is the placeholder to do it.
CLIENTS must not set 'do_not_alter' flag; leave it to default.
The client should only define one request message. If the client includes multiple requests here, the server may pick/choose an arbitrary one. NOTE: The erlang protobuffs compiler doesn't support 'oneof'. But 'oneof' appears to be a very tiny memory optimization that not all languages might care about? (Erlang doesn't)
TODO: If we wish to support pipelined requests sometime in the future, this is the placeholder to do it.
Generic error response, typically used when something quite bad/unexpected happened within the server. Clients should always check this response and, if defined, ignore any request-specific response at codes 10+.
Specific responses.
Used in:
Used in:
Used in:
Used in: