Large data sets

2009-10-06 Thread Brenden Matthews
Hi, In the documentation here: http://code.google.com/apis/protocolbuffers/docs/techniques.html#large-data it specifies that if you are dealing in messages larger than a megabyte each, it may be time to consider an alternate strategy. My question is: does this apply to messages which are

Message::ByteSize() wrong

2009-10-07 Thread Brenden Matthews
The value returned by Message::ByteSize() does not match the actually number of bytes that are consumed after writing a message to a stream. Example: some_message m; /* ... populate m ... */ size_t len = m.ByteSize(); int pos =

Re: Message::ByteSize() wrong

2009-10-07 Thread Brenden Matthews
be broken. Can you provide a complete example program that demonstrates your problem? On Wed, Oct 7, 2009 at 4:01 PM, Brenden Matthews bren...@diddyinc.comwrote: The value returned by Message::ByteSize() does not match the actually number of bytes that are consumed after writing a message

Re: Message::ByteSize() wrong

2009-10-07 Thread Brenden Matthews
On Wed, Oct 7, 2009 at 6:48 PM, Henner Zeller h.zel...@acm.org wrote: Still haven't run it (I only seem to have a too old cmake; a simple Makefile with a .proto and .cc file showing the problem would be better. Please strip down the example if someone should help debugging it ;) ) Anyway,

[protobuf] [PATCH] Display non-present fields with TextFormat.

2010-11-23 Thread Brenden Matthews
edf13be13766caa1a496c9feeced8d9d24de0c10 Mon Sep 17 00:00:00 2001 From: Brenden Matthews bren...@diddyinc.com Date: Tue, 23 Nov 2010 17:01:01 -0800 Subject: [PATCH] Display non-present fields with TextFormat. This allows for the non-presence of optional fields to be represented in string output

[protobuf] Re: [PATCH] Display non-present fields with TextFormat.

2010-11-23 Thread Brenden Matthews
On Tue, Nov 23, 2010 at 5:04 PM, Brenden Matthews bren...@diddyinc.comwrote: Greetings, One of the best features of protocol buffers is the notion of presence. Another great feature is the ability to do 'message.PrintDebugString()'. One problem, however, is that fields which