Re: [Boost-users] [serialization] Transactional persistence ?

Buster wrote:

For one, it seems to require that you serialize the entire container each time you change one element. Perhaps I'm wrong ?

Nope, you're correct. This is a fundamental feature of the library

The other problem is that I don't see anything related to transactions within the library. This may even prevent me from using the library to implement the actual serialization of each element, as I wouldn't be able to gurantee that the data was NOT written. Unless one can hook up transactional archives to boost serialization ?

Nothing is written to an archive until one explictly invokes the appropriate operator. Robert Ramey