It depends entirely what you want to represent :)
A big pb is useful if you need to avoid network latency and can't pipeline the
data. But it isn't trivial to pick arbitrary sub-objects out of a big pb - you
essentially need to process all the leading data.
Of course, with the right prefixes, a sequence of small messages on the same
stream is identical to a single pb with a repeated member.
Marc
On 26 Mar 2011, at 16:08, alf wrote:
> I recognize each case is different but for your experience what is
> best
>
> to do a big pb with a lot of data serialized or split in several
> smaller pb.
>
> thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to protobuf@googlegroups.com.
> To unsubscribe from this group, send email to
> protobuf+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/protobuf?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
