Comment #6 on issue 374 by Add method in ByteString to avoid big buffer copy.

I'm a little perplexed here. Protobuf is both intended to be used to transport all your data, but at the same time it can't handle large amounts of data (vis a vis large byte fields).

So, you want to use protobuf to carry your RPC data for a database? The solution seems to be adding out-of-band data that trails your protobuf RPC 'header'. For example, the work done in HBase: (

Maybe someone at Google could give a little insight as to how Bigtable uses protobuf to carry all the data traffic but also not suffer the insane penalty that comment #5 hints at?

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

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 post to this group, send email to
Visit this group at
For more options, visit

Reply via email to