[binarycloud-dev] Implementing version control/history

[Alok K. D. <al...@dh...>]

Hello all - I'm seriously considering adopting r2 as the basis for a
fairly sophisticatede knowledge management system which will manage
several object classes (entities) including documents, events, people,
tasks, etc.  One of the project requirements is full version
control/edit histories on any object data.  I.e. when you make edits to
object data and save it, the changed object is stored as a 'new' object,
with a same unique identifier as the previous version, and the previous
version is marked as inactive.  This effectively will allow us to build
an interface with the ability for automatic version control, unlimited
undo, and so on.

Having read through the pre-release docs on r2, it doesn't look like
there's anything in the core product which will facilitate this.  On the
other hand, there also doesn't seem to be anything which should hinder
this.

I'm curious to hear comments from the developer community on the
feasibility of implementing this requirement using bc r2.

Seems to me that this functionality may belong in the core product, with
parameters in the XML entity definition files that would enable
versioning/history automatically.  Comments?

Thanks.

Al