Lines Matching refs:RPC

6 ``pw_rpc`` can generate services which encode/decode RPC requests and responses
46 Take the following RPC service as an example.
83     // Implementations of the service's RPC methods; see below.
86 Unary RPC
88 A unary RPC is implemented as a function which takes in the RPC's request struct
98 Server streaming RPC
100 A server streaming RPC receives the client's request message alongside a
119   Closes the stream and sends back the RPC's overall status to the client.
126   avoid accidentally closing it and ending the RPC.
128 Client streaming RPC
134 Bidirectional streaming RPC
159 The ``NanopbClientCall`` object returned by the RPC invocation stores the active
160 RPC's context. For more information on ``ClientCall`` objects, refer to the
161 :ref:`core RPC documentation <module-pw_rpc-making-calls>`.
165 RPC responses are sent back to the caller through a response handler object.
166 These are classes with virtual callback functions implemented by the RPC caller
167 to handle RPC events.
172 Unary / client streaming RPC
188     // Called when an error occurs internally in the RPC client or server.
194   A handler for RPC methods which return a single response (i.e. unary and
204   Callback invoked if an internal error occurs in the RPC system. Optional;
226 Server streaming / bidirectional streaming RPC
241     // Called when the server ends the stream with the overall RPC status.
244     // Called when an error occurs internally in the RPC client or server.
250   A handler for RPC methods which return zero or more responses (i.e. server
260   the RPC.
264   Callback invoked if an internal error occurs in the RPC system. Optional;
288 The following example demonstrates how to call an RPC method using a nanopb
304     // The RPC will remain active as long as `call` is alive.