Subject: Re: [boost] [persistent] Persistent library preview
From: Stefan Strasser (strasser_at_[hidden])
Date: 2010-01-08 10:32:50
Am Friday 08 January 2010 14:07:46 schrieb Peder Holt:
> if that is acceptable to your use case and other use cases you can think of
> > I'll at it to the "future development" page.
> > I don't think it's an essential part of such a library and necessary for
> > the
> > initial version of it.
> This is acceptable to my use case.
what I wrote in my previous emails, that changesets could be checked for
conflicts, is incorrect though.
the user of such an interface would have to make sure that the data an undo
changeset reverses has not been used for anything (that is not undone).
> > but you seem to be experienced in implementing undo/redo so you're
> > welcome to draft a public interface for this.
> > the implementation would be pretty easy I think. the information that
> > describes the changes made by a transaction is already available while a
> > transaction is running.
> I'll look into it.
> Thanks for your time
this is an interesting feature because some other stuff can be implemented on
top of it, like database replication, by sending the changesets to a remote
system and applying it there. or incremental backup.
so thanks for pushing me towards that idea.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk