Bazaar for a web-based CMS

[Ralf Kistner]

I'm developing a web-based content management system in Python, and would like to use bazaar to manage the content.

This is my proposed model:
 - A main branch where the content is stored (central repository, no trees)
 - A lightweight checkout where the content is accessed from
 - Each user has his own branch

All these are stored on the same server. These steps are followed when a user edits 'n page on the site:
 - The file in the user's branch is modified.
 - When the user is done, the changes are committed (to the user's branch)
 - A merge is run on the user's branch, and any conflicts are resolved, and committed
 - The user's branch is pushed to the central repository
 - The lightweight checkout is updated to reflect the changes

A user can also do a checkout of his branch on the server to make local edits, the rest of the process is the same.


Would this model work?

Is it better to use a central repository with trees, and access the data from there, or a lightweight checkout as in my proposed model?

One problem I have with this model is that it might not scale well: if there are thousands of pages and many users, it's not ideal to keep a complete up-to-date branch for each user. So is it possible at all to only store the modified files in the user branches?

How does concurrent operations work in Bazaar? What happens if two users try to commit (different files) at the same time?

Any help will be appreciated.

Regards,
Ralf Kistner