[protobuf] Re: How to speedup serialization and deserialization process?

Marc, Thank you very much for the detailed explanation. I got it. Due to curiosity, I tried manual explicit serialization. I needed to code more but indeed it worked way faster as you suggested. Thanks again for the wonderful explanation. - Ravi On Wednesday, December 20, 2017 at 10:00:31

Re: [protobuf] Merge serialized and non-serialized protobuf

Another thing you could do is create another message which exactly matches WrapperContent except that it stores a bytes field instead of the Content field, like this: message WrapperContentBytes { required string metatData = 1; required bytes content = 2; } Then you can just stick the

Re: [protobuf] Merge serialized and non-serialized protobuf

You can simply prepending the serialized tag and length before the serialized data of content. Say, content is 0x0A0B0C0D, the you just prepend 0x12 (number is 2, type is length-delimited) and 0x04 (content is 4 bytes long). So 0x12040A0B0C0D will be the data for wrapper. On Fri, Jan 26, 2018 at

[protobuf] How to merge a serialized protobuf with a another protobuf without deserializing the first

I'm trying to understand if it's possible to take a serialized protobuf that makes up part of another protobuf and merge them together without having to deserialize the first protobuf. For example, given a protobuf wrapper: syntax = "proto2"; import "content.proto"; message WrapperContent

[protobuf] Merge serialized and non-serialized protobuf

I'm trying to understand if it's possible to take a serialized protobuf that makes up part of another protobuf and merge them together without having to deserialize the first protobuf. For example, given a protobuf wrapper: syntax = "proto2"; import "content.proto"; message WrapperContent

Re: [protobuf] Generating c++ code with prefixes or sufixes for enums

Unfortunately there is no flag to prefix enums this way. I have run into a similar problem and the best solution I found was to just pass a flag to the compiler to undefine the problematic macro. On Fri, Jan 19, 2018 at 12:35 AM, Illya Galashko wrote: > Hi, > I have

Re: [protobuf] an error occurs when I build for Android ARM: reference to 'map' is ambiguous

Great, I'm glad that worked--that was just a guess, but I happen to have a pull request that will fully qualify types like std::map and std::pair, instead of relying on "using" statements in common.h: https://github.com/google/protobuf/pull/4209 So once I get that pull request merged, the problem

Re: [protobuf] Precompiled Version of probuf for VS2017

Protoc is available for multiple OSes here: https://github.com/google/protobuf/releases/tag/v3.5.1 Note sure about pre-compiled libs; for Java, they're on mvnrepository; for C# they're on NuGet, etc. On 26 January 2018 at 15:22, 'Frank Willen' via Protocol Buffers < protobuf@googlegroups.com>

[protobuf] Precompiled Version of probuf for VS2017

Hi, I want to use the protocol buffers for a mixed solution (C+, C#, both in VS2017). Where can I download precompiled libs, headers and the protoc.exe? Or is it neccessary to build the probuffers for everyone? Thanks for your support? Grettings Frank -- You received this message because