Archive for the ‘chandlerdb’ Category

The Chandler transaction model

Monday, June 7th, 2004

Chandler’s repository enables concurrent and versioned access to the items it stores. The repository keeps the history of all changes made to items over their lifetime. This history can be used to replay or revert changes made to an item. It makes undoing committed transactions possible. It makes automated merging of different versions possible.

(more…)

Pinning items into memory

Thursday, June 3rd, 2004

OSAF chose a non-locking transaction model for Chandler’s repository.
One advantage of that choice is that items are never locked.
(more…)

find() API changes

Sunday, May 30th, 2004

Because of syntactic overlap between path strings and uuid strings the find() API on Item and Repository had to be reworked.

(more…)

Proposal for ref collection-based paths

Monday, May 24th, 2004

Natively, the repository supports two ways of finding any item, by Universally Unique IDentifier (UUID) and by Path.
(more…)