On Jan 13, 2011, at 4:38 , Meghana wrote:
Is there any way of working around this problem?
You can increase the limit with CodedInputStream.setSizeLimit, which
is an easy route. The problem is that the performance is bad for
really large messages, because the whole thing needs to be serialized/
deserialized to/from a single buffer.
The "high performance" version would be to encode your own simple
protocol. Something like:
1. Write the number of messages with writeRawVarint32
2. Write each message with writeDelimitedTo
On the decoding side, do the opposite. I'm not familiar with the
framework you are using, but this should be feasible. Hope this helps,
You received this message because you are subscribed to the Google Groups "Protocol
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at