Default package

Get desktop application:
View/edit binary Protocol Buffers messages

* This message is used for Protobuf Rpc Engine. The message is used to marshal a Rpc-request from RPC client to the RPC server. The Response to the Rpc call (including errors) are handled as part of the standard Rpc response.

• required string methodName = 1

  * Name of the RPC method

• optional bytes request = 2

  * Bytes corresponding to the client protobuf request

• required string declaringClassProtocolName = 3

  * protocol name of class declaring the called method

• required uint64 clientProtocolVersion = 4

  * protocol version of class declaring the called method

* RpcKind determine the rpcEngine and the serialization of the rpc payload

Used in: RpcPayloadHeaderProto

• RPC_BUILTIN = 0

  Used for built in calls by tests

• RPC_WRITABLE = 1

  Use WritableRpcEngine

• RPC_PROTOCOL_BUFFER = 2

  Use ProtobufRpcEngine

the header for the RpcRequest

• optional RpcKindProto rpcKind = 1

• optional RpcPayloadOperationProto rpcOp = 2

• required uint32 callId = 3

  each rpc has a callId that is also used in response

Used in: RpcPayloadHeaderProto

• RPC_FINAL_PAYLOAD = 0

  The final payload

• RPC_CONTINUATION_PAYLOAD = 1

  not implemented yet

• RPC_CLOSE_CONNECTION = 2

  close the rpc connection

* Rpc Response Header - If successfull then the Respose follows after this header - length (4 byte int), followed by the response - If error or fatal - the exception info follow - length (4 byte int) Class name of exception - UTF-8 string - length (4 byte int) Stacktrace - UTF-8 string - if the strings are null then the length is -1 In case of Fatal error then the respose contains the Serverside's IPC version

• required uint32 callId = 1

  callId used in Request

• required RpcStatusProto status = 2

• optional uint32 serverIpcVersionNum = 3

  in case of an fatal IPC error

Used in: RpcResponseHeaderProto

• SUCCESS = 0

  RPC succeeded

• ERROR = 1

  RPC Failed

• FATAL = 2

  Fatal error - connection is closed