tcamuso wrote
Problem is that the time to process the files this way is O(log n), ....
I would think that this is solvable, but I can't really comment without spending significant time looking at the specific code.
If there were linefeeds in the serialized data, the code to do this would be much simpler.
I don't even remember if there should be line feeds in there. certainly xml archives have linefeeds. But again, I'd have to spend a lot of time looking at your specific case. Of course you could hire me by the hour if you like.
Is there another, more architected way for me to deserialize an aggregate of serializations?
I think what you want to do should be possible in an efficient way. However, it would require spending enough time with the library to understand how it works at a deeper level. I realized that this defeats the original appeal of the library to some extent. But it's still better than writing a new system from scratch. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/Serialization-cumulatively-tp4673059p4673... Sent from the Boost - Users mailing list archive at Nabble.com.