| /aosp_15_r20/external/pigweed/pw_rpc/ |
| H A D | protocol.rst | 9 Pigweed RPC servers and clients communicate using ``pw_rpc`` packets. These
15 Pigweed RPC packets consist of a type and a set of fields. The packets are
23 The packet type and RPC type determine which fields are present in a Pigweed RPC
32 | REQUEST | Invoke an RPC |
65 | CLIENT_ERROR | Abort an ongoing RPC |
83 status codes result in the same action by the server: aborting the RPC.
85 * ``CANCELLED`` -- The client requested that the RPC be cancelled.
86 * ``ABORTED`` -- The RPC was aborted due its channel being closed.
92 * ``INVALID_ARGUMENT`` -- The server sent a packet type to an RPC that does not
93 support it (a ``SERVER_STREAM`` was sent to an RPC with no server stream).
[all …]
|
| H A D | cpp.rst | 13 RPC server
19 The following size report showcases the memory usage of the core RPC server. It
28 RPC server implementation
33 The RPC Server depends on the ``pw::rpc::internal::Method`` class. ``Method``
35 RPC functions. Each supported protobuf implementation extends ``Method`` to
97 RPC client
99 The RPC client is used to send requests to a server and manages the contexts of
108 To send incoming RPC packets from the transport layer to be processed by a
123 // Called when the transport layer receives an RPC packet.
138 Making RPC calls
[all …]
|
| H A D | design.rst | 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
[all …]
|
| H A D | guides.rst | 17 of the RPC lifecycle.
19 1. RPC service declaration
81 2. RPC code generation
101 For example, the generated RPC header for ``applications/blinky.proto`` is
105 The generated header defines a base class for each RPC service declared in the
111 3. RPC service definition
113 Implement a service class by inheriting from the generated RPC service
114 base class and defining a method for each RPC. The methods must match the name
177 The generated code includes RPC service implementation stubs. You can
183 #. Locate the generated RPC header in the build directory. For example:
[all …]
|
| /aosp_15_r20/external/grpc-grpc/examples/python/retry/ |
| H A D | README.md | 26 The client RPC will succeed, even with server injecting multiple errors. Here is an example server …
31 INFO:root:Injecting error to RPC from ipv6:[::1]:54471
32 INFO:root:Successfully responding to RPC from ipv6:[::1]:54473
33 INFO:root:Injecting error to RPC from ipv6:[::1]:54491
34 INFO:root:Injecting error to RPC from ipv6:[::1]:54581
35 INFO:root:Injecting error to RPC from ipv6:[::1]:54581
36 INFO:root:Injecting error to RPC from ipv6:[::1]:54581
37 INFO:root:Injecting error to RPC from ipv6:[::1]:54581
38 INFO:root:Successfully responding to RPC from ipv6:[::1]:54581
39 INFO:root:Injecting error to RPC from ipv6:[::1]:55474
[all …]
|
| /aosp_15_r20/external/pigweed/pw_rpc/ts/ |
| H A D | docs.rst | 10 easier to work with if you are using the RPC via HDLC over WebSerial.
16 Creating an RPC Client
18 The RPC client is instantiated from a list of channels and a set of protos.
44 Finding an RPC Method
46 Once the client is instantiated with the correct proto library, the target RPC
56 The four possible RPC stubs are ``UnaryMethodStub``,
62 Invoke an RPC with callbacks
73 All RPC methods can be invoked with a set of callbacks that are triggered when
74 either a response is received, the RPC is completed, or an error occurs. The
75 example below demonstrates registering these callbacks on a Bidirectional RPC.
[all …]
|
| /aosp_15_r20/external/pytorch/docs/source/ |
| H A D | rpc.rst | 3 Distributed RPC Framework
6 The distributed RPC framework provides mechanisms for multi-machine model
12 APIs in the RPC package are stable. There are multiple ongoing work items
17 Not all features of the RPC package are yet compatible with CUDA support and
29 The distributed RPC framework makes it easy to run functions remotely, supports
32 across RPC boundaries. These features can be categorized into four sets of APIs.
34 1) **Remote Procedure Call (RPC)** supports running a function on the specified
36 or creating a reference to the return value. There are three main RPC APIs:
68 across RPC boundaries and in which order should the local autograd engines
70 inter-dependent RPC calls in the forward pass.
[all …]
|
| /aosp_15_r20/external/pigweed/pw_rpc/pwpb/ |
| H A D | docs.rst | 11 ``pw_rpc`` can generate services which encode/decode RPC requests and responses
47 All examples in this document use the following RPC service definition.
84 // Implementations of the service's RPC methods; see below.
87 Unary RPC
89 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
118 Closes the stream and sends back the RPC's overall status to the client.
122 Closes the stream and sends back the RPC's overall status to the client only
130 avoid accidentally closing it and ending the RPC.
[all …]
|
| /aosp_15_r20/external/pigweed/pw_rpc/nanopb/ |
| H A D | docs.rst | 6 ``pw_rpc`` can generate services which encode/decode RPC requests and responses
46 All examples in this document use the following RPC service definition.
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.
123 Closes the stream and sends back the RPC's overall status to the client only
131 avoid accidentally closing it and ending the RPC.
[all …]
|
| /aosp_15_r20/external/grpc-grpc/examples/python/cancellation/ |
| H A D | README.md | 16 A client may cancel an RPC for several reasons. Perhaps the data it requested
20 ##### Cancelling a Server-Side Unary RPC from the Client
22 The default RPC methods on a stub will simply return the result of an RPC.
32 to be executed when the RPC completes, or to cancel the RPC before it has
35 In the example, we use this interface to cancel our in-progress RPC when the
55 ##### Cancelling a Server-Side Streaming RPC from the Client
57 Cancelling a Server-side streaming RPC is even simpler from the perspective of
60 iterate over it to yield the results of our RPC.
83 It may also decide to cancel the RPC for its own reasons. In our example, the
84 server can be configured to cancel an RPC after a certain number of hashes has
[all …]
|
| /aosp_15_r20/external/python/cpython2/Doc/library/ |
| D | xmlrpclib.rst | 1 :mod:`xmlrpclib` --- XML-RPC client access
5 :synopsis: XML-RPC client access.
24 XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP(S) as a
27 supports writing XML-RPC client code; it handles all the details of translating
45 remote XML-RPC server. The required first argument is a URI (Uniform Resource
55 a commonly-used extension to the XML-RPC specification, but isn't supported by
66 the remote server as part of the connection process when invoking an XML-RPC
73 corresponding RPC calls on the remote server. If the remote server supports the
85 | XML-RPC type | Python type |
115 This is the full set of data types supported by XML-RPC. Method calls may also
[all …]
|
| D | simplexmlrpcserver.rst | 1 :mod:`SimpleXMLRPCServer` --- Basic XML-RPC server
5 :synopsis: Basic XML-RPC server implementation.
22 XML-RPC servers written in Python. Servers can either be free standing, using
30 functions that can be called by the XML-RPC protocol. The *requestHandler*
36 on to :mod:`xmlrpclib` and control the XML-RPC responses that will be returned
51 Create a new instance to handle XML-RPC requests in a CGI environment. The
53 control the XML-RPC responses that will be returned from the server.
75 alone XML-RPC servers.
80 Register a function that can respond to XML-RPC requests. If *name* is given,
120 Registers the XML-RPC introspection functions ``system.listMethods``,
[all …]
|
| D | docxmlrpcserver.rst | 1 :mod:`DocXMLRPCServer` --- Self-documenting XML-RPC server
5 :synopsis: Self-documenting XML-RPC server implementation.
32 Create a new instance to handle XML-RPC requests in a CGI environment.
37 Create a new request handler instance. This request handler supports XML-RPC
50 self-documenting, stand alone XML-RPC servers. HTTP POST requests are handled as
51 XML-RPC method calls. HTTP GET requests are handled by generating pydoc-style
79 creating self-documenting, XML-RPC CGI scripts. HTTP POST requests are handled
80 as XML-RPC method calls. HTTP GET requests are handled by generating pydoc-style
|
| /aosp_15_r20/external/grpc-grpc/src/python/grpcio/grpc/_cython/_cygrpc/aio/ |
| H A D | call.pyx.pxi | 20 _UNKNOWN_CANCELLATION_DETAILS = 'RPC cancelled for unknown reason.'
21 _OK_CALL_REPRESENTATION = ('<{} of RPC that terminated with:\n'
26 _NON_OK_CALL_REPRESENTATION = ('<{} of RPC that terminated with:\n'
70 """Assembles the RPC representation string."""
100 """Creates the corresponding Core object for this RPC.
183 """Cancels the RPC in Core with given RPC status.
214 """Returns if the RPC call has finished.
217 because the RPC finished or because was cancelled..
220 True if the RPC can be considered finished.
225 """Returns if the RPC was cancelled.
[all …]
|
| /aosp_15_r20/external/google-cloud-java/java-analytics-admin/proto-google-analytics-admin-v1alpha/src/main/proto/google/analytics/admin/v1alpha/ |
| H A D | analytics_admin.proto | 1353 // Request message for GetAccount RPC.
1366 // Request message for ListAccounts RPC.
1386 // Request message for ListAccounts RPC.
1396 // Request message for DeleteAccount RPC.
1409 // Request message for UpdateAccount RPC.
1423 // Request message for ProvisionAccountTicket RPC.
1433 // Response message for ProvisionAccountTicket RPC.
1439 // Request message for GetProperty RPC.
1452 // Request message for ListProperties RPC.
1490 // Response message for ListProperties RPC.
[all …]
|
| /aosp_15_r20/external/googleapis/google/analytics/admin/v1alpha/ |
| H A D | analytics_admin.proto | 1566 // Request message for GetAccount RPC.
1579 // Request message for ListAccounts RPC.
1599 // Request message for ListAccounts RPC.
1609 // Request message for DeleteAccount RPC.
1622 // Request message for UpdateAccount RPC.
1636 // Request message for ProvisionAccountTicket RPC.
1646 // Response message for ProvisionAccountTicket RPC.
1652 // Request message for GetProperty RPC.
1665 // Request message for ListProperties RPC.
1703 // Response message for ListProperties RPC.
[all …]
|
| /aosp_15_r20/external/python/cpython3/Doc/library/ |
| D | xmlrpc.client.rst | 1 :mod:`xmlrpc.client` --- XML-RPC client access
5 :synopsis: XML-RPC client access.
17 XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP(S) as a
20 supports writing XML-RPC client code; it handles all the details of translating
42 remote XML-RPC server. The required first argument is a URI (Uniform Resource
52 a commonly used extension to the XML-RPC specification, but isn't supported by
76 the remote server as part of the connection process when invoking an XML-RPC
83 corresponding RPC calls on the remote server. If the remote server supports the
95 | XML-RPC type | Python type |
132 This is the full set of data types supported by XML-RPC. Method calls may also
[all …]
|
| D | xmlrpc.server.rst | 1 :mod:`xmlrpc.server` --- Basic XML-RPC servers
5 :synopsis: Basic XML-RPC server implementations.
14 The :mod:`xmlrpc.server` module provides a basic server framework for XML-RPC
33 functions that can be called by the XML-RPC protocol. The *requestHandler*
39 on to :mod:`xmlrpc.client` and control the XML-RPC responses that will be returned
55 Create a new instance to handle XML-RPC requests in a CGI environment. The
57 and control the XML-RPC responses that will be returned from the server.
80 alone XML-RPC servers.
85 Register a function that can respond to XML-RPC requests. If *name* is given,
127 Registers the XML-RPC introspection functions ``system.listMethods``,
[all …]
|
| /aosp_15_r20/external/pigweed/pw_rpc_transport/ |
| H A D | docs.rst | 13 (RPCs) on a device. It does not include any transports for sending these RPC
20 uniquely identifies both sides of an RPC conversation. It allows developers to
22 what framing will be used to send RPC packets over those transports.
26 Framed RPC data ready to be sent via ``RpcFrameSender``. Consists of a header
27 and a payload. Some RPC transport encodings may not require a header and put
31 A single RPC packet can be split into multiple ``RpcFrame``'s depending on the
34 All frames for an RPC packet are expected to be sent and received in order
39 Sends RPC frames over some communication channel (e.g. a hardware mailbox,
45 ``RpcPacketEncoder`` is used to split and frame an RPC packet.
51 Provides means of sending an RPC packet to its destination. Typically it ties
[all …]
|
| /aosp_15_r20/external/googleapis/google/analytics/admin/v1beta/ |
| H A D | analytics_admin.proto | 648 // Request message for GetAccount RPC.
661 // Request message for ListAccounts RPC.
681 // Request message for ListAccounts RPC.
691 // Request message for DeleteAccount RPC.
704 // Request message for UpdateAccount RPC.
718 // Request message for ProvisionAccountTicket RPC.
728 // Response message for ProvisionAccountTicket RPC.
734 // Request message for GetProperty RPC.
747 // Request message for ListProperties RPC.
785 // Response message for ListProperties RPC.
[all …]
|
| /aosp_15_r20/external/pigweed/pw_log_rpc/ |
| H A D | docs.rst | 8 An RPC-based logging solution for Pigweed with log filtering and log drops
15 RPC Logging
20 1. Set up RPC
22 Set up RPC for your target device. Basic deployments run RPC over a UART, with
38 Create an ``RpcLogDrainMap`` with one ``RpcLogDrain`` for each RPC channel used
41 with the application's RPC service. The ``RpcLogDrainMap`` provides a convenient
55 Logging over RPC diagrams
58 Sample RPC logs request
60 The log listener, e.g. a computer, requests logs via RPC. The log service
71 Sample logging over RPC
[all …]
|
| /aosp_15_r20/external/google-cloud-java/java-analytics-admin/proto-google-analytics-admin-v1beta/src/main/proto/google/analytics/admin/v1beta/ |
| H A D | analytics_admin.proto | 638 // Request message for GetAccount RPC.
651 // Request message for ListAccounts RPC.
671 // Request message for ListAccounts RPC.
681 // Request message for DeleteAccount RPC.
694 // Request message for UpdateAccount RPC.
708 // Request message for ProvisionAccountTicket RPC.
718 // Response message for ProvisionAccountTicket RPC.
724 // Request message for GetProperty RPC.
737 // Request message for ListProperties RPC.
775 // Response message for ListProperties RPC.
[all …]
|
| /aosp_15_r20/external/mobly-snippet-lib/examples/ex7_default_and_optional_rpc/ |
| H A D | README.md | 4 into Mobly snippet lib to annotate RPC's parameters.
9 RPC methods, which allows developers to create more flexible and reusable RPC
14 - Improve the readability and maintainability of RPC methods.
16 - Make it easier to test RPC methods.
39 didn't provide a Boolean to the RPC, so a default value, true, is used.
44 provide a Boolean to the RPC, so the value is used instead of using
51 pass a value to the RPC.
|
| /aosp_15_r20/external/pigweed/pw_hdlc/rpc_example/ |
| H A D | docs.rst | 4 RPC over HDLC example
14 the RPC over HDLC example.
17 sends HDLC-encoded RPC packets via ``pw_sys_io``. It has blocking sends and
19 mostly serves as a simplistic example for quickly bringing up RPC over HDLC
68 The RPC console uses :ref:`module-pw_console` to make a rich interactive
69 console for working with ``pw_rpc``. Run the RPC console with the following
79 organized by their protocol buffer package and RPC service, as defined in a
91 RPCs may also be invoked from Python scripts. Close the RPC console if it is
109 Local RPC example project
135 In a separate Pigweed-activated terminal, run the ``pw-system-console`` RPC
[all …]
|
| /aosp_15_r20/external/grpc-grpc/examples/python/wait_for_ready/ |
| H A D | README.md | 3 The default behavior of an RPC is to fail instantly if the server is not ready yet. This example de…
7 > If an RPC is issued but the channel is in TRANSIENT_FAILURE or SHUTDOWN states, the RPC is unable…
9 …RPC option to not fail RPCs as a result of the channel being in TRANSIENT_FAILURE state. Instead, …
16 …clients and servers at the same time, it is very like to fail first couple RPC calls due to unavai…
18 …orary unavailability of the server. With 'wait-for-ready' semantics, those RPC calls will automati…
24 # Per RPC level
|