On Wednesday, March 13, 2013 7:36:18 PM UTC-7, Sumit Kumar wrote: > > Int32 and such will see endianness issues when exchanging messages > in-between cross-endian platforms hence only byte type suffices. > Not a problem when you are using protobufs.
> > On how we achieve fixed length string support once byte type is supported > - Just create a message with specific number of byte elements and can name > it like fixed8String instead. Accessors can be added via simple plugin that > uses protoc insert point. > > Regards, > Sumit Kumar > > On 13 Mar, 2013, at 8:38 PM, Giri Guntipalli > <[email protected]<javascript:>> > wrote: > > we need similar thing to hold binary data in proto message, where i can > not use string because binary data may have the null character in middle > > > On Tuesday, 29 January 2013 14:30:31 UTC+5:30, [email protected]: >> >> >> Comment #3 on issue 269 by [email protected]: Would like to have byte >> or >> int8 type for the message definition >> http://code.google.com/p/protobuf/issues/detail?id=269 >> >> Re kumar.sumit: >> How are you going to use the byte field to implement a fixed length >> string? >> If byte can, why can't int32? >> >> -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected]<javascript:> > . > Visit this group at http://groups.google.com/group/protobuf?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/protobuf?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
