[protobuf] Issue 381 in protobuf: Do not use heap where stack can be used

2012-04-03 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 381 by nn1436...@gmail.com: Do not use heap where stack can be used http://code.google.com/p/protobuf/issues/detail?id=381 In generated code you see following lines: ImportMessageLite::default_instance_ = new

[protobuf] Re: Protocol Buffers for IOS

2012-04-03 Thread Nicola Ferruzzi
> Is there any direct support for Protocol Buffers  in iOS? (armv6, > armv7) > > I have gone through he following > link..http://code.google.com/p/metasyntactic/wiki/ProtocolBuffers > > It uses v2.2 and currently available version is v2.4 I use latest version in my app .. you don't really need o

Re: [protobuf] Fast navigation in binary gzip'ed file that includes messages of variable length

2012-04-03 Thread Jason Hsueh
In general protobuf doesn't try to provide these kinds of container formats. Gzip*Stream is meant to deal with data that is valid gzip; inserting frames to make it searchable would break the format. In the archives you may find other references to the internal container file format that Google has;

Re: [protobuf] Fast navigation in binary gzip'ed file that includes messages of variable length

2012-04-03 Thread Igor Gatis
Similarly to what Jason suggested, you may have summary blocks which lets you quick inspect value ranges. Like: message Record { optional int id = 1;   //  fields only you know about. } message RecordBlock {   repeated Record record = 1; // You could declare these as 'bytes' type