Re: [protobuf] How to use oneOf as a type?

oneof is a property of the message that the fields are in; it's not really a type of its own. Instead, you could do something like message Event { required int32 event_id = 1; optional EventSpecifics specifics = 2; } message EventSpecifics { oneof EventType { optional FooEvent

Re: [protobuf] How to calculate protobuf size?

The simplest way would be to serialize your messages into bytes and then measure the size directly, right? On Sun, Dec 10, 2017 at 11:26 AM, Tomer Praizler wrote: > Couldn't find a nice and easy way to calculate my protobuf sizes using > python. Is there a recommended

Re: [protobuf] Is there being a way to modify/define the .proto file with python?

an extend caffe.LayerParameter by your self, > given that LayerParameter allows extension. > > On Wed, Jun 21, 2017 at 1:12 AM Brian Palmer <bpal...@gmail.com> wrote: > >> Hi, >> >> it sounds to me like you should explore defining a new message that >>

Re: [protobuf] Is there being a way to modify/define the .proto file with python?

Hi, it sounds to me like you should explore defining a new message that contains the LayerParameter as a field. For example, syntax = "proto2"; package lynxcommando; message AugmentedLayerParameter { optional caffe.LayerParameter base = 1; optional MyNewParameter my_new_parameter = 2; }

Re: [protobuf] How to distinguish between messages?

On Sun, Feb 19, 2017 at 5:26 PM pbaranov wrote: > It's probably something trivial but I can't figure it out :( I have 2 > messages that have similar structure and when I try to encode message #1 > and decode it as message #2 it works just fine. Why??? If that's how it is

Re: [protobuf] Number of Bits Written to Memory

On Thu, Feb 3, 2011 at 8:58 AM, Tanya turtle...@gmail.com wrote: Basically, we need some way of specifying how the bytes are encoded/ written to memory, and we need to specify the number of bits written each time. Is this possible to do in protocol buffers? And if so, how would it be

Re: [protobuf] New Ruby Protocol Buffers library

) a general-purpose landing page? On Thu, Oct 21, 2010 at 10:02 AM, Brian Palmer br...@codekitchen.net wrote: Mozy has just open sourced their implementation of Protocol Buffers for Ruby. The implementation has been in use internally at Mozy for over a year. This implementation has put a lot of focus

[protobuf] New Ruby Protocol Buffers library

/mozy/ruby-protocol-buffers The gem: https://rubygems.org/gems/ruby-protocol-buffers The docs: http://rubydoc.info/gems/ruby-protocol-buffers/0.8.4/frames -- Brian Palmer -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group