| /external/chromium-trace/catapult/third_party/gsutil/third_party/protorpc/experimental/javascript/ |
| D | protorpc.js | 42 ProtoRpc.RPC = function(service_path, method_name, request, success, error) { class in ProtoRpc
58 this.setState_(ProtoRpc.RPC.State.REQUEST_ERROR);
61 xhr.setRequestHeader('Content-Type', ProtoRpc.RPC.CONTENT_TYPE);
72 this.setState_(ProtoRpc.RPC.State.REQUEST_ERROR);
83 ProtoRpc.RPC.State = {
97 ProtoRpc.RPC.CONTENT_TYPE = 'application/json;charset=utf-8';
105 ProtoRpc.RPC.prototype.xhr_ = null;
113 ProtoRpc.RPC.prototype.successCallback_ = null;
121 ProtoRpc.RPC.prototype.errorCallback_ = null;
129 ProtoRpc.RPC.prototype.request_ = null;
[all …]
|
| /external/llvm/tools/lli/ |
| D | RemoteTargetExternal.h | 32 RPCChannel RPC; variable
35 return RPC.WriteBytes(Data, Size); in WriteBytes()
38 bool ReadBytes(void *Data, size_t Size) { return RPC.ReadBytes(Data, Size); } in ReadBytes()
91 RPC.ChildName = ChildName; in create()
92 if (!RPC.createServer()) in create()
|
| D | RemoteTargetExternal.cpp | 116 RPC.Wait(); in stop()
|
| /external/llvm/tools/lli/ChildTarget/ |
| D | ChildTarget.cpp | 20 RPCChannel RPC; member in LLIChildTarget
37 return RPC.WriteBytes(Data, Size) ? Size : -1; in WriteBytes()
40 return RPC.ReadBytes(Data, Size) ? Size : -1; in ReadBytes()
63 RPC.createClient(); in initialize()
|
| /external/sl4a/ |
| D | README.md | 44 b) To enable RPC access from the command prompt:
58 contains which RPC functions are available in SL4A as well as documentation
59 for the RPC functions.
|
| /external/chromium-trace/catapult/third_party/WebOb/docs/ |
| D | jsonrpc-example.txt | 1 JSON-RPC Example
12 example shows how to create a `JSON-RPC <http://json-rpc.org/>`_
18 While this example presents JSON-RPC, this is not an endorsement of
19 JSON-RPC. In fact I don't like JSON-RPC. It's unnecessarily
20 un-RESTful, and modelled too closely on `XML-RPC
34 JSON-RPC wraps an object, allowing you to call methods on that object
39 <http://json-rpc.org/wd/JSON-RPC-1-1-WD-20060807.html>`_ goes into the
488 "Error from JSON-RPC client %s: %s"
637 ProxyError: Error from JSON-RPC client http://localhost:8080: 400 Bad Request
639 Here the exception isn't a JSON-RPC method exception, but a more basic
|
| /external/autotest/frontend/afe/doctests/ |
| D | 002_site_rpc_test.txt | 1 # This file is for site-specific doctests of the AFE RPC interface.
|
| D | 003_misc_rpc_features.txt | 1 # this doctest contains tests for miscellaneous features of the RPC interface
|
| D | 001_rpc_test.txt | 4 # a bit of setup to allow overriding rpc_interace with an RPC proxy
5 # (to use RPC, we would say
|
| /external/protobuf/ |
| D | CHANGES.txt | 146 * The RPC (cc|java|py)_generic_services default value is now false instead of
214 * The generic RPC service code generated by the C++, Java, and Python
220 particular RPC implementation.
401 needed by RPC server implementations.
402 * RPC interfaces now support blocking operation in addition to non-blocking.
404 which operate against separate blocking and non-blocking RPC interfaces.
405 RPC implementations will have to implement the new interfaces in order to
422 * Updated RPC interfaces to allow for blocking operation. A client may
423 now pass None for a callback when making an RPC, in which case the
426 cannot be used in practice until RPC implementations are updated to
|
| D | README.android | 11 of its internal RPC protocols and file formats.
|
| /external/cros/system_api/dbus/cryptohome/ |
| D | rpc.proto | 10 // 'optional' annotations are used heavily in the RPC definition
11 // because the RPC endpoints most properly sanity check the contents
73 // These parameters are for inbound data to Cryptohome RPC
|
| /external/chromium-trace/catapult/third_party/gsutil/third_party/protorpc/protorpc/experimental/parser/ |
| D | protobuf_lexer.g | 45 RPC : 'rpc';
|
| D | protobuf.g | 113 : RPC id '(' qualified_name ')'
|
| /external/autotest/ |
| D | global_config.ini | 109 # Turn on RPC Logging
117 # Transfer RPC logs to a RPC logging server
375 # running inside the container can use the same user to make RPC.
|
| /external/autotest/client/site_tests/documentscan_AppTestWithFakeLorgnette/ |
| D | control | 38 this test. It will accept the D-Bus RPC calls that Chrome makes
|
| /external/llvm/tools/lli/Unix/ |
| D | RPCChannel.inc | 102 llvm::errs() << "RPC Error: " << Desc << ": " << ErrorMsg << '\n';
|
| /external/skia/ |
| D | DEPS | 51 # Mojo SDK for Mojo RPC experiments.
|
| /external/nanopb-c/generator/proto/google/protobuf/ |
| D | descriptor.proto | 287 // are not specific to any particular RPC system. They are generated by the
293 // that generate code specific to your particular RPC system. Therefore,
445 // Note: Field numbers 1 through 32 are reserved for Google's internal RPC
459 // Note: Field numbers 1 through 32 are reserved for Google's internal RPC
|
| /external/tcpdump/ |
| D | INSTALL.txt | 197 rpc_auth.h - definitions for ONC RPC authentication
198 rpc_msg.h - definitions for ONC RPC messages
|
| /external/llvm/lib/Target/Hexagon/ |
| D | HexagonBitTracker.cpp | 365 RegisterCell RPC = RegisterCell::self(Reg[0].Reg, W0); in evaluate() local
366 RPC.fill(0, 2, BT::BitValue::Zero); in evaluate()
367 return rr0(eADD(RPC, eIMM(im(2), W0)), Outputs); in evaluate()
|
| /external/protobuf/src/google/protobuf/ |
| D | descriptor.proto | 315 // are not specific to any particular RPC system. They are generated by the
321 // that generate code specific to your particular RPC system. Therefore,
503 // Note: Field numbers 1 through 32 are reserved for Google's internal RPC
523 // Note: Field numbers 1 through 32 are reserved for Google's internal RPC
|
| D | unittest_custom_options.proto | 111 // A test RPC service with custom options at all possible locations (and also
|
| /external/valgrind/docs/internals/ |
| D | Darwin-notes.txt | 127 look at notes in coregrind/Makefile.am re Mach RPC interface
|
| /external/dbus/doc/ |
| D | dcop-howto.txt | 24 that X is required. CORBA was thought to be a more effective IPC/RPC
43 DCOP is a simple IPC/RPC mechanism built to operate over sockets.
146 called function, but you will not hang while the RPC is processed either.
|