I'd have to go back and review the details, but originally persistent-
objects had additional functionality for user-generated slots and the
slot access protocol that differed from persistent-collection.
persistent - provides functionality for anything which is resident in
the data store - basically oid and controller references.
persistent-object (persistent) - provides a base class for anything
using the persistent object protocol for slot accesses.
persistent-collection (persistent) - inherits directly from persistent
and is a placeholder for methods or data common to all collections
(for now that's basically nothing).
Ian
On Jun 15, 2008, at 12:55 PM, Glenn Tarcea wrote:
Hey guys, I'm trying to understand why user classes inherit from
persistent-object, rather than persistent (that is why is there a
distinction and separation of functionality). I can see that the
initialization for persistent-object uses more of the elephant
classes (eg, all the different kinds of slot), and it kind of looks
like internal Elephant classes that need access to the underlying
infrastructure but don't need transient slots, etc... use persistent
and then have greater control over the rest. Am I on the right track?
Thanks,
Glenn
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
