Comments on: Revision Control for Web Application Content

By: Zakaria

Zakaria — Tue, 27 Jun 2006 08:59:20 +0000

In Software Engineering for Internet Applications
(a guide that every web developer must read)
on Content Management chapter also address this issues
http://philip.greenspun.com/seia/content-management

By: Saya

Saya — Mon, 26 Jun 2006 21:03:45 +0000

Great article!
Some questions popped up in my mind:
* How to handle conflict during merge (if any), present the conflict to the user?
* How to split the table in multiple repositories? Say, I want to store the old revisions in other server to save space but I want them still to be accessible.

By: DiN

DiN — Mon, 26 Jun 2006 16:15:46 +0000

A CMS called Drupal (http://drupal.org) already has this feature. ;)

The contents are stored in ‘node’ table and — similarly — the revisions are stored in ‘node_revisions’.

There are differences to your concept:
- ‘status’ is in stored in ‘node’, not ‘node_revisions’
- a revision is stored not automatically. In drupal, an edit can be stored as revision or just publish (in order to save space).