However, in order to implement this refactoring, the application code has to stop using the repository directly. That is, Chandler items will not inherit from repository code, nor use repository notifications to implement calculated attributes, check types, manage birefs, etc.
I think repository notifications have been a huge win. Obviously we use them too much -- especially in the calendar, which we should (and can easily) improve. However, I think getting rid of them is a mistake.
I think it isn't obvious that object relational mapping is faster than persisting whole objects. If you don't believe me on this point go spend some time Googling the subject.
John _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
