Lines Matching refs:RPC

19 RPC call lifecycle
21 In ``pw_rpc``, an RPC begins when the client sends an initial packet. The server
23 RPC function. The RPC is considered active until the server sends a status to
24 finish the RPC. The client may terminate an ongoing RPC by cancelling it.
25 Multiple concurrent RPC requests to the same method may be made simultaneously
29 Depending the type of RPC, the client and server exchange zero or more protobuf
30 request or response payloads. There are four RPC types:
45 The key events in the RPC lifecycle are:
47 * **Start**. The client initiates the RPC. The server's RPC body executes.
48 * **Finish**. The server sends a status and completes the RPC. The client calls
52   request and it is handled when the RPC starts.
55   only one response and it is handled when the RPC completes.
56 * **Error**. The server or client terminates the RPC abnormally with a status.
104 a client. This is useful in testing and in situations like an RPC that triggers
108 The C++ API for opening a server reader/writer takes the generated RPC function
110 passed as arguments. The API is the same for all RPC types, except the
115    // Open a ServerWriter for a server streaming RPC.
119    // Send some responses, even though the client has not yet called this RPC.
123    // Finish the RPC.