I'm not sure what you mean by general purpose serialization, but I'm
pretty sure Protocol Buffers is what I'd use for it.
Very deep trees just call for a different layout when serialized, e.g.
flatten the nodes to a list with each node containing the index of its
parent node.
On Sun, Dec 27,
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
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
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.
