Hey all,
Happy holidays first of all. I'm new to protocol buffers, but from
what I've worked with, it's pretty cool!
I was recently tasked (for another project) with investigating the use
of protocol buffers with netty (http://jboss.org/netty) as an
alternative RPC implementation to apache's thri
./configure CXXFLAGS='-O0 -ggdb3'
Instead of stepping through the protobuf code, though, I'd recommend is that
you add some code to your own project to read the bytes directly from the
istream and then verify that they are the same bytes that were originally
produced by the protobuf serializer. Y
Thanks for your help - I found that I was exceeding the recursion
limit in CodedInputStream. I was able to instantiate my own
CodedInputStream and increase the limit, but it would be nice if some
sort of error was printed when the limit is exceeded.
On Mon, Dec 28, 2009 at 9:52 AM, Kenton Varda w
Huh, I thought we did print a message there, but I guess not.
That said, you're the first person I've ever heard of who hit that limit
with (presumably) legitimate data. Consider designing you protocol
differently? The limit exists for security reasons (to avoid stack
overflows), so simply bumpi
I understand why it's there, and it makes sense for apps in general. I
admit I'm using proto bufs for general serialization purposes within
my app rather than the over-the-wire communication tool it was
designed as. It just seems much easier to use than
boost::serialization or other alternatives. W