protocol-buffers

I am prototyping Protobuf-net to replace some of our existing C# code which is currently using [Datacontract] to Serialize objects to Xml. Using protobuffer we can easily share data with Java. I am thus very interested in the .proto file generation of Protobuf-net. This worked well for almost all the use cases I tested so far. But now with inheritance it's a different ball game. The .proto file that's been generated for the Inherited classes is very simple - not including any of the fields for the Base Class. The inheritance itself is working fine in C# - I can read the generated byte stream

I am trying to reduce the number of methods that are generated by Google proto-buf and one of the alternatives is to use proto-buf nano. However I found no documentation on how to use it. Except the package link , I can't find anything on how to generate java files from proto files using nano. So the question is straight-forward: how to use google proto nano in order to generate java classes from proto files and how to use them in a project? Looking at the main protobuf compiler source code: #include <google/protobuf/compiler/javanano/javanano_generator.h> .... int main(int argc, char* argv[])

I have a .proto file definition which needs to import "google/protobuf/descriptor.proto" because I use Custom Options . So in my .proto file I do: import "google/protobuf/descriptor.proto"; package ...; ... Since my file didn't compile complaining about the dependency, I got a copy of the descriptor.proto file placing it in the same directory my proto file was. This solved the problem but I don't believe this is the correct way. Now the descriptor.proto gets compiled together with my .proto file resulting in having 2 compiled descriptor.proto at runtime: the one shipped with the protobuf-java

I would like to include a protocol definition file in another protocol file. For example: // base.proto: message P_EndPoint { required int32 id = 1; required string host = 2; required int32 port = 3; } Then in another file: communication.proto: // somehow include `base.proto' // ... message P_CommunicationProtocol { required CP_MessageType type = 1; optional int32 id = 2; optional P_EndPoint identity = 3; repeated P_EndPoint others = 4; } // ... (Note: developers.google.com is not available in my locale) import "myproject/base.proto"; Docs: http://developers.google.com/protocol-buffers/docs

I am currently trying to use Tensorflow's shared library in a non-bazel project, so I creat a .so file from tensorflow using bazel. but when I launch a c++ program that uses both Opencv and Tensorflow, it makes me the following error : [libprotobuf FATAL external/protobuf/src/google/protobuf/stubs/common.cc:78] This program was compiled against version 2.6.1 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.1.0). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of

Currently I have a RESTful web service with endpoints that are exposed via Jersey/JAX-RS: @Path("/widgets") public class WidgetResource { @GET List<Widget> getAllWidgets() { // gets Widgets somehow } @POST Widget save(Widget w) { // Save widget and return it } } I use Jackson for serializing/deserializing my POJOs into JSON, and my service both responds to and sends back my POJOs as application/json . I am now looking to possibly use Google protocol buffers (or an equivalent technology) to help compress/optimize the communication between client and service, as JSON/text is pretty bulky

This is kind of a branch off of my other question . Read it if you like, but it's not necessary. Basically, I realized that in order to effectively use C#'s BeginReceive() on large messages, I need to either (a) read the packet length first, then read exactly that many bytes or (b) use an end-of-packet delimiter. My question is, are either of these present in protocol buffers? I haven't used them yet, but going over the documentation it doesn't seem like there is a length header or a delimiter. If not, what should I do? Should I just build the message then prefix/suffix it with the length