@Kevin, Yes, Go binding is pure go, but requires the C library which handles the logic/communication with master etc. Similar approach with the Java binding (and probably the Python one). Nevertheless, it works.
On Wed, Apr 9, 2014 at 7:18 AM, Kevin Lyda <ke...@ie.suberic.net> wrote: > On Wed, Apr 9, 2014 at 11:39 AM, Vladimir Vivien > <vladimir.viv...@gmail.com> wrote: > > Thank you for clarifying. I thought the low-level api being referred in > the > > video had to do with communication between master and framework|executor > > for scheduling. But, it's really administrative. I thought that would > > have been an opportunity for a Go binding that did not require the C++ > > libraries. > > The go protobuf support requires the protoc tool (which is written in > C++) but I'm pretty sure the code generated is pure go code. I > haven't built any go code with protobufs in it, but just from reading > the docs and looking at the proto library code I don't see any linkage > to C++. > > So you need a C++ coded tool to generate code, but the result is pure Go. > > Kevin > > -- > Kevin Lyda > Galway, Ireland > US Citizen overseas? We can vote. > Register now: http://www.votefromabroad.org/ > -- Vladimir Vivien
