Cloud-based item deletion
Wednesday, February 2nd, 2005As with item copying Item clouds can now be used to define a set of items to delete together.
(more…)As with item copying Item clouds can now be used to define a set of items to delete together.
(more…)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.
(more…)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.
(more…)
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.
(more…)In order to support
Item Stamping, the data model had to be enhanced to support changing an item’s kind on the fly.
(more…)
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…
(more…)
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.
(more…)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.
(more…)