language issues: how to add the concept of persistence to an existing language such as Java; this leads to ideas such as OrthogonalPersistence, Transactions, PersistenceByReachability and RootsOfPersistence, PersistenceByDeclaration (is there a standard term for this?)
implementation issues: how to implement the underlying storage manager at the lowest level. A PersistentStore may take many forms. One approach is to use an existing database (eg. use a relational DB and perform object<->relation mapping as is done by commercial products such as that from Thought Inc http://www.thoughtinc.com and DB Visual Architect http://www.visual-paradigm.com/dbva.php ); another is to build an object store in the similar manner as Mneme or the Texas Persistent Store ( http://www.cs.utexas.edu/users/oops/papers.html#texas ). The Texas Persistent Store uses PointerSwizzling, perhaps in a similar to how the commercial OODB ObjectStore does it.
integration issues: RelationalDatabase as our object store, native support for it into our ObjectOriented OS, a file system for objects with "build-in" support for the object/relational impedance problem.
Content of these pages are owned and copyrighted by the poster.