Whilst working on the protobuf protocol, it was found that there was a common set of "client protocol" stuff that was not protobuf specific. Splitting out these common pieces of code, now allows for a cleaner, more targeted protobuf (serialization) specific implementation. It also provides a platform where the community can implement their own client serialization mechanism, (i.e messagePack, avro ) with minimal effort and code invasiveness.
Geode-protobuf is the protobuf specific implementation of the client protocol. --Udo On Fri, Nov 3, 2017 at 10:20 AM, Anthony Baker <[email protected]> wrote: > What is the difference between these two submodules: > > geode-protobuf > geode-client-protocol > > ? > > Thanks, > Anthony > > > On Nov 3, 2017, at 9:22 AM, Galen O'Sullivan <[email protected]> > wrote: > > > > It may be that we missed one of the places where a module gets linked in. > > Where did you see this error? > > > > On Fri, Nov 3, 2017 at 9:20 AM, Kirk Lund <[email protected]> wrote: > > > >> Anyone know why the build is failing in geode-assembly? > >> > >> * What went wrong: > >> A problem occurred evaluating project ':geode-assembly'. > >>> Project with path ':geode-client-protocol' could not be found in > project > >> ':geode-assembly'. > >> > > -- Kindest Regards ----------------------------- *Udo Kohlmeyer* | *Pivotal* [email protected] <http://www.gopivotal.com/> www.pivotal.io
