|
|
| (3 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
|
| |
|
| A common question that comes up is "How can I communicate with olad using something other than C++, Python or Java?".
| |
|
| |
|
| | | This page has moved to [[doc:rpc_system|here]]. |
| == Intro ==
| |
| | |
| OLA is a client / server architecture. The clients and the server (olad) communicate over a TCP socket. By default olad listens on localhost:9010. Data passed between the client and the server is serialized using [https://developers.google.com/protocol-buffers/ Protocol Buffers]. The [https://developers.google.com/protocol-buffers/docs/overview overview] and [https://developers.google.com/protocol-buffers/docs/encoding data encoding] pages describe the specifics of the serialization process.
| |
| | |
| To write a new client at the very least you need an implementation of protocol buffers for your language. Luckily there is widespread support for protocol buffers in [https://code.google.com/p/protobuf/wiki/ThirdPartyAddOns many languages].
| |
| | |
| == Simple Example ==
| |
| | |
| From <tt>common/rpc/Rpc.proto</tt>,
| |
| | |
| <pre>
| |
| message RpcMessage {
| |
| required Type type = 1;
| |
| optional uint32 id = 2;
| |
| optional string name = 3;
| |
| optional bytes buffer = 4;
| |
| }
| |
| </pre>
| |
| | |
| | |
| common/protocol/
| |
Latest revision as of 14:05, 30 March 2014
This page has moved to here.
