Mercurial > hg > piper-cpp
comparison vamp-client/CapnpRRClient.h @ 100:bbb99f94e225
Serialisation, comments
author | Chris Cannam <c.cannam@qmul.ac.uk> |
---|---|
date | Fri, 14 Oct 2016 12:46:38 +0100 |
parents | 427c4c725085 |
children | 8c449824e08d |
comparison
equal
deleted
inserted
replaced
99:b2ec891c22b9 | 100:bbb99f94e225 |
---|---|
13 #include <capnp/serialize.h> | 13 #include <capnp/serialize.h> |
14 | 14 |
15 namespace piper_vamp { | 15 namespace piper_vamp { |
16 namespace client { | 16 namespace client { |
17 | 17 |
18 /** | |
19 * Client for a request-response Piper server, i.e. using the | |
20 * RpcRequest/RpcResponse structures with a single process call rather | |
21 * than having individual RPC methods, with a synchronous transport | |
22 * such as a subprocess pipe arrangement. Only one request can be | |
23 * handled at a time. This class is thread-safe if and only if it is | |
24 * constructed with a thread-safe SynchronousTransport implementation. | |
25 */ | |
18 class CapnpRRClient : public PluginClient, | 26 class CapnpRRClient : public PluginClient, |
19 public Loader | 27 public Loader |
20 { | 28 { |
21 // unsigned to avoid undefined behaviour on possible wrap | 29 // unsigned to avoid undefined behaviour on possible wrap |
22 typedef uint32_t ReqId; | 30 typedef uint32_t ReqId; |