Home
last modified time | relevance | path

Searched refs:RPC (Results 1 – 16 of 16) sorted by relevance

/external/llvm/tools/lli/
DRemoteTargetExternal.h32 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()
DRemoteTargetExternal.cpp116 RPC.Wait(); in stop()
/external/llvm/tools/lli/ChildTarget/
DChildTarget.cpp20 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/chromium-trace/trace-viewer/third_party/WebOb/docs/
Djsonrpc-example.txt1 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/protobuf/
DCHANGES.txt146 * 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
DREADME.android11 of its internal RPC protocols and file formats.
/external/llvm/tools/lli/Unix/
DRPCChannel.inc102 llvm::errs() << "RPC Error: " << Desc << ": " << ErrorMsg << '\n';
/external/tcpdump/
DINSTALL.txt132 pmap_prot.h - definitions for ONC RPC portmapper protocol
230 rpc_auth.h - definitions for ONC RPC authentication
231 rpc_msg.h - definitions for ONC RPC messages
DCHANGES680 aren't big enough to be a RPC. As noted by David Sacerdote.
/external/nanopb-c/generator/proto/google/protobuf/
Ddescriptor.proto287 // 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/protobuf/src/google/protobuf/
Ddescriptor.proto315 // are not specific to any particular RPC system. They are generated by the
321 // that generate code specific to your particular RPC system. Therefore,
500 // Note: Field numbers 1 through 32 are reserved for Google's internal RPC
520 // Note: Field numbers 1 through 32 are reserved for Google's internal RPC
Dunittest_custom_options.proto111 // A test RPC service with custom options at all possible locations (and also
Dunittest.proto846 // Test that RPC services work.
/external/valgrind/docs/internals/
DDarwin-notes.txt134 look at notes in coregrind/Makefile.am re Mach RPC interface
/external/libxml2/
DTODO261 representation of the document. Even better using RPC's
/external/iproute2/doc/
Dss.sgml79 <tt/rpcbind/. RPC services are prefixed with <tt/rpc./