| /external/pigweed/pw_rpc/nanopb/ |
| D | docs.rst | 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
[all …]
|
| /external/pigweed/pw_rpc/ |
| D | docs.rst | 27 Creating an RPC
30 1. RPC service declaration
100 2. RPC code generation
116 For example, the generated RPC header for ``"foo_bar/the_service.proto"`` is
120 The generated header defines a base class for each RPC service declared in the
126 3. RPC service definition
128 The serivce class is implemented by inheriting from the generated RPC service
129 base class and defining a method for each RPC. The methods must match the name
135 The generated code includes RPC service implementation stubs. You can
141 #. Locate the generated RPC header in the build directory. For example:
[all …]
|
| /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 | 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
|
| 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 …]
|
| /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
40 remote XML-RPC server. The required first argument is a URI (Uniform Resource
50 a commonly-used extension to the XML-RPC specification, but isn't supported by
74 the remote server as part of the connection process when invoking an XML-RPC
81 corresponding RPC calls on the remote server. If the remote server supports the
93 | XML-RPC type | Python type |
130 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
32 functions that can be called by the XML-RPC protocol. The *requestHandler*
38 on to :mod:`xmlrpc.client` and control the XML-RPC responses that will be returned
54 Create a new instance to handle XML-RPC requests in a CGI environment. The
56 and control the XML-RPC responses that will be returned from the server.
79 alone XML-RPC servers.
84 Register a function that can respond to XML-RPC requests. If *name* is given,
126 Registers the XML-RPC introspection functions ``system.listMethods``,
[all …]
|
| /external/grpc-grpc/src/objective-c/examples/SwiftSample/ |
| D | ViewController.swift | 50 var RPC : GRPCProtoCall! // Needed to convince Swift to capture by reference (__block) in viewDidLoad() variable
51 RPC = service.rpcToUnaryCall(with: request) { response, error in in viewDidLoad()
62 RPC.requestHeaders["My-Header"] = "My value" in viewDidLoad()
64 RPC.start() in viewDidLoad()
|
| /external/perfetto/src/trace_processor/rpc/ |
| D | README.md | 1 # TraceProcessor RPC
3 This directory contains the RPC interfaces to use the Perfetto Trace Processor
13 The HTTP RPC module. It exposes a protobuf-over-HTTP RPC interface that allows
|
| /external/pigweed/pw_hdlc/rpc_example/ |
| D | docs.rst | 4 RPC over HDLC example project
9 interactively and with a script using the RPC over HDLC example.
49 The RPC console uses `IPython <https://ipython.org>`_ to make a rich interactive
50 console for working with pw_rpc. Run the RPC console with the following command,
60 or globs for .proto files that define the RPC services to support:
71 An example echo RPC command:
78 organized by their protocol buffer package and RPC service, as defined in a
90 RPCs may also be invoked from Python scripts. Close the RPC console if it is
103 Local RPC example project
|
| /external/grpc-grpc/doc/ |
| D | wait-for-ready.md | 4 If an RPC is issued but the channel is in `TRANSIENT_FAILURE` or `SHUTDOWN`
5 states, the RPC is unable to be transmited promptly. By default, gRPC
10 gRPC implementations MAY provide a per-RPC option to not fail RPCs as a result
14 as the channel is `SHUTDOWN` or the RPC's deadline is reached.
|
| D | internationalization.md | 4 As a universal RPC framework, gRPC needs to be fully usable within/across different international e…
12 ### Method name (in RPC Invocation)
19 ### Host name (in RPC Invocation)
26 ### Status detail/message (accompanies RPC status code)
|
| /external/grpc-grpc/test/core/tsi/alts/fake_handshaker/ |
| D | transport_security_common.proto | 29 // Max and min supported RPC protocol versions.
31 // RPC version contains a major version and a minor version.
36 // Maximum supported RPC version.
38 // Minimum supported RPC version.
|
| /external/grpc-grpc-java/alts/src/main/proto/grpc/gcp/ |
| D | transport_security_common.proto | 29 // Max and min supported RPC protocol versions.
31 // RPC version contains a major version and a minor version.
36 // Maximum supported RPC version.
38 // Minimum supported RPC version.
|
| /external/grpc-grpc/src/core/tsi/alts/handshaker/proto/ |
| D | transport_security_common.proto | 29 // Max and min supported RPC protocol versions.
31 // RPC version contains a major version and a minor version.
36 // Maximum supported RPC version.
38 // Minimum supported RPC version.
|
| /external/rust/crates/grpcio-sys/grpc/src/core/tsi/alts/handshaker/proto/ |
| D | transport_security_common.proto | 29 // Max and min supported RPC protocol versions.
31 // RPC version contains a major version and a minor version.
36 // Maximum supported RPC version.
38 // Minimum supported RPC version.
|
| /external/autotest/server/site_tests/firmware_FAFTRPC/ |
| D | control.all | 9 PURPOSE = "Verify that the RPC server, and all RPC functions, work as expected."
10 CRITERIA = "This test will fail if the FAFT RPC system is not set up correctly."
18 This test checks that all RPC functions on all subsystems are connected,
|
| /external/rust/crates/grpcio-sys/grpc/src/proto/grpc/gcp/ |
| D | transport_security_common.proto | 35 // Max and min supported RPC protocol versions.
37 // RPC version contains a major version and a minor version.
42 // Maximum supported RPC version.
44 // Minimum supported RPC version.
|
| /external/grpc-grpc-java/testing-proto/src/main/proto/io/grpc/testing/protobuf/ |
| D | simpleservice.proto | 28 // Simple unary RPC.
31 // Simple client-to-server streaming RPC.
34 // Simple server-to-client streaming RPC.
37 // Simple bidirectional streaming RPC.
|
| /external/grpc-grpc/examples/objective-c/auth_sample/ |
| D | MakeRPCViewController.m | 29 // Category for RPC errors to create the descriptions as we want them to appear on our view.
43 return [NSString stringWithFormat:@"Unexpected RPC error %li: %@",
60 // Create a not-yet-started RPC. We want to set the request headers on this object before starting
78 // Start the RPC.
81 self.mainLabel.text = @"Waiting for RPC to complete...";
|
| /external/perfetto/src/tracing/ |
| D | README.md | 18 ## Option 2) Using the provided UNIX RPC transport
19 The `include/unix_rpc` provides the building blocks necessary to implement a RPC
28 ## Option 3) Providing a custom RPC transport
31 implementation that can be transferred through RPC. Concrete example of this is
52 platform-specific things like implementation of shared memory and RPC mechanism.
|
| /external/ltp/testcases/network/rpc/rpc-tirpc/ |
| D | README | 3 *** RPC and TI-RPC Test Suite for Unix and Linux ***
47 * runtest/net.rpc_tests - for TS-RPC testing
48 * runtest/net.tirpc_tests - for TI-RPC testing
|
| /external/python/cpython3/Lib/idlelib/ |
| D | CREDITS.txt | 10 Schneider-Kamp and Nicholas Riley. David wrote the first version of the RPC
12 the RPC code and Remote Debugger currently integrated in IDLE. Bruce Sherwood
18 the integration of the RPC and remote debugger, implemented the threaded
23 Noam Raphael (Code Context, Call Tips, many other patches), and Chui Tey (RPC
|
| /external/pigweed/pw_rpc/internal/ |
| D | packet.proto | 32 // The client received a packet for an RPC it did not request.
43 // A server streaming or bidirectional RPC has completed.
58 // associated. For RPC packets, this is the service that processes the packet.
67 // Status code for the RPC response or error.
|
| /external/python/cpython2/Lib/idlelib/ |
| D | CREDITS.txt | 10 Schneider-Kamp and Nicholas Riley. David wrote the first version of the RPC
12 the RPC code and Remote Debugger currently integrated in IDLE. Bruce Sherwood
18 the integration of the RPC and remote debugger, implemented the threaded
23 Noam Raphael (Code Context, Call Tips, many other patches), and Chui Tey (RPC
|