Replace proto compilation with protostuff-runtime

[abailly]

This is a follow-up to #44 (and #46).

In order to remove dependency from barge-core to protocol buffer, we could use protostuff in barge-proto-rpc to be able to expose only POJOs in the API and still use that POJOs as protocol buffer messages.

[mgodave]

I'm not familiar with protostuff. Do you have a hard dependency to remove protobuf? I'm OK with the coupling otherwise.

[abailly]

Neither am I anymore (been using it couple of years ago...). Not sure what your second sentence means but if you are asking whether or not I have some strong requirement to remove protobuf then the answer is no. I find this is a great library when one wants to ensure interoperability in heterogeneous platforms: We have been using it at work for a mixed C++/Java middleware. It is efficient, clever and well supported.

However my point is that going from .proto to .java induces a coupling in the way barge's domain objects are modelled and used, with a dependency towards what protobuf is able to handle. Besides it adds complexity to the build at a point where it is needed. I would rather focus on bulletproofing the core protocol and this will be easier with a tiny core implemented in full java.

[mgodave]

👍