Hi,
Is there a facility in protobuf library to retrieve data if the field
numbers and wire types are known? If so how to go about this?
Regards,
Rahul
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Protocol
How do I represent java.util.Date in my .proto definition? Is this
supported, or any other workaround for doing this?
Regards,
Rahul Prasad
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Protocol Buffers group
, Henner Zeller h.zel...@acm.org wrote:
Seems to be part of Android
http://www.google.com/codesearch?q=com.google.common.io.protocol.ProtoBuf
On Tue, Nov 10, 2009 at 11:36, Kenton Varda ken...@google.com wrote:
On Tue, Nov 10, 2009 at 7:28 AM, rahul prasad rahu...@gmail.com wrote:
Hi,
May i
I am in a situation, where the .proto files are not present for the Protocol
Buffers used in the application I am working on. Since the .proto files need
to be created, I was wondering if the following yellow highlighted numbers
should correspond to the same fields they stood for in the actual
If I try to grab and read the protocol buffer I populated, I see in the logs
where I am outputting, characters like Z especially occuring at places
where I had added another protobuf to the exisiting protobuf. Can you
explain what it's purpose is and how does this occur?
rahul
, double 2
Length-delimitedstring, bytes, embedded messages, packed repeated
fields3Start groupgroups (deprecated)4End groupgroups
(deprecated)532-bitfixed32, sfixed32, float
Regards,
Rahul Prasad
--~--~-~--~~~---~--~~
You received this message because you
and other
ambiguities you mentioned below have to be done manually though)
Regards,
Rahul Prasad
On Sat, Nov 14, 2009 at 3:57 PM, Marc Gravell marc.grav...@gmail.comwrote:
If you treat it as a string (UTF8), you are likely to get garbage. If you
treat it as a byte[], then you just get a BLOB
, but it
worked for me. Thanks.
Regards,
Rahul Prasad
On Mon, Nov 16, 2009 at 1:42 PM, Jason Hsueh jas...@google.com wrote:
You can decode the protocol buffer with just wire type + tag number, but
you won't know the original types without a proto definition. Everything
would be treated
