On Tue, Nov 30, 2010 at 1:21 PM, Evan Jones <ev...@mit.edu> wrote:
> * I'll guess that it will not be slower if you access all the strings.
> Currently, the parsing process copies the raw bytes from the input buffer
> into an individual byte array, then converts that to a String. This is,
> sadly, the most efficient thing you can do, since you need "special" code to
> create Strings. Therefore, doing "lazy" conversion isn't going to be slower.
> The objects already have both byte and String fields for each string due
> to an encoding improvement I contributed, so this should be nearly a pure
BTW, we actually ended up reverting your change and replacing it with the
new implementation. We found that having two references increased memory
pressure too much. I thought I had mentioned this to you; sorry if I
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at