Re: [binarycloud-dev] Implementing version control/history

[John P. C. <jp...@jp...>]

On Sat, Sep 22, 2001 at 11:24:42PM -0400, Alok K. Dhir wrote:
> 
> 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.

We have a few versioned entities.  We basically implement and override the 
necessary methods in the derived class.  For example, the
VersionedObjectManager::Set() can do whatever you want or you can just call the
parent::Add() and get the system default behaviour.  It's not automatic, but
functional.

> 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?

If it's possible to spec out the behaviour of a generic versioned object in a
way that is useful for the majority of the cases, then this is very feasible. 

jpc