Comment #6 on issue 374 by [email protected]: Add method in ByteString to
avoid big buffer copy.
http://code.google.com/p/protobuf/issues/detail?id=374
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:
(http://hbase.apache.org/book/apjs03.html).
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:
https://code.google.com/hosting/settings
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/groups/opt_out.
