snap thoughts

In AgileWiki2, the snap utility was simple. It created a log file which reflected current state (no history) and then you rebuilt the database using only that log file. This let us keep the database to a reasonable size, though at the cost of losing all history. Good enough for a prototype, but there are situations where it simply will not do.

What you really want is the ability to create a snapshot for an eariler time, like the beginning of the previous month. Now you can keep some history. And this is important when sharing content--sharing depends on the change history.

As for how to do this, I'm thinking that the snap utility should be kept as simple as possible--it just creates a log-like snap file reflecting the state of the database at a past time. Then the restore utility uses the snap file together with selected content from the log file to create an up-to-date database with limited history.

Seems doable.

Bill