As with item copying Item clouds can now be used to define a set of items to delete together.

Read the rest of this entry »

An attribute monitor is a method defined on an item that is invoked when something happens to the attribute(s) it registered an interest in. That invocation is synchronous and reacts to changes on items in the same repository view as the item of the method being invoked.

Read the rest of this entry »

A year and a half ago, when the Chandler repository project was (re-)started, I chose to use Sleepycat’s Berkeley DB and DBXML for the persistence layer. Read the rest of this entry »

The transaction model chosen for Chandler’s repository calls for item version merging. In the Chandler 0.4 release, version merging is mostly implemented, with a few notable exceptions.

Read the rest of this entry »

As said in an earlier post, ref collections are implemented as a double-linked list of bi-directional item references. Ref collection indexes enhance ref collections by enabling positional access into them.

Read the rest of this entry »

The constructor on an Item instance is only invoked the first time the instance is created. It is not invoked as the item is re-instantiated when loaded from the repository.

Read the rest of this entry »

In order to support Item Stamping, the data model had to be enhanced to support changing an item’s kind on the fly. Read the rest of this entry »

Item clouds are a way of semantically grouping together items of different kinds not otherwise stored together in a ref collection or otherwise. For example, the constitutive parts of an email in Chandler are items of various kinds such as the headers, the body, the attachments etc… Read the rest of this entry »

As with the rest of Chandler, its repository is a work in progress. This is reflected in the state of the various documents pertaining to it. This post attempts to list the known and maintained sources of repository documentation.

Read the rest of this entry »

Ref collections, double-linked lists of bi-directional item references, are backed by a hashtable keyed on the referenced items UUIDs. Ref collections - designed with scalability in mind - are sparsely loaded into memory on an as-needed basis. Read the rest of this entry »