The archive is, by design, insensitive of the application type. What you need to decide is whether one of the archive types is suitable for your application though. You have binary, text, and xml archive choices without creating a new archive type. I can imagine the necessity to create a new archive type if, for instance: o you wanted to save all versions of a document. o you needed to conform to some specific file format. o you needed to stick the document into a database The only small caviot that I've discovered with boost.serialization is its handling of pointers to primative data types. It is sometimes necessary to write a wrapper class around such data to make it non-primative. std::string is such a type. Martin Slater wrote:
Robert Ramey wrote:
I can't see why this would require a new archive type
Now that would be perfect if I did not need a new archive type, I'm having trouble envisioning how it would work without one though. Any chance you could explain a bit more?
thanks
Martin