[Jackrabbit Wiki] Update of "PersistenceManagerFAQ" by RoyFielding

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by RoyFielding:
http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ

The comment on the change is:
uncamelcased

------------------------------------------------------------------------------
- = PersistenceManager(PM) FAQ =
+ = Persistence Manager (PM) FAQ =
+ 
  The responses were mainly gathered from the jackrabbit mailing list. 
  
  === What's a PM? ===
@@ -14, +15 @@

  A PM should not be 'intelligent', it should not 'interpret' the data. The only thing it should care about is to efficiently, consistently and reliably store and read the data encapsulated in the passed nodeState & propertyState objects. Though it might be feasible to write a custom persistence manager to represent existing legacy data in a level-1 (read-only) repository, I don't think the same is possible for a level-2 repository and i certainly would not recommend it.
  
  === What combination of FS and PM is the best choice? ===
- It depends on your priorities. If you want to store your data in a RDBMS, use SimpleDbPersistenceManager + either LocalFileSystem or DbFileSystem. If you want to store your data in an accessible format (just in case ;), you might want to try XMLPersistenceManager + LocalFileSystem. If you use windows and performance is a must, you might want to try ObjectPersistenceManager + CQFileSystem.
+ It depends on your priorities. If you want to store your data in a RDBMS, use Simple``Db``Persistence``Manager + either Local``File``System or Db``File``System. If you want to store your data in an accessible format (just in case ;), you might want to try XML``Persistence``Manager + Local``File``System. If you use windows and performance is a must, you might want to try Object``Persistence``Manager + CQ``File``System.
  
  === Which are the current options? What are the status, pros and cons of each implementation? ===
  
- === SimpleDbPersistenceManager (and subclasses thereof) ===
+ === Simple``Db``Persistence``Manager (and subclasses thereof) ===
   * Status: mature
   * the jackrabbit default persistence manager
   * JDBC based
   * zero-deployment, schema is automatically created
   * transactional
  
- === ObjectPersistenceManager ===
+ === Object``Persistence``Manager ===
   * Status: mature
-  * persists data in an abstract FileSystem using a simple binary serialization format
+  * persists data in an abstract File``System using a simple binary serialization format
   * easy to configure
   * if the jvm process is killed the repository might turn inconsistent
   * non transactional
  
- === XMLPersistenceManager ===
+ === XML``Persistence``Manager ===
   * Status: mature
-  * persists data in an abstract FileSystem using XML serialization format
+  * persists data in an abstract File``System using XML serialization format
   * not meant to be used in production enviroments
   * easy to configure
   * if the jvm process is killed the repository might turn inconsistent
   * non transactional
  
- === ORMPersistenceManager ===
+ === ORM``Persistence``Manager ===
   * Status: experimental & unfinished, still being maintained?
   * Not so simple
   * transactional
   * rdbms referential integrity (possible, but not implemented yet)
   * not so easy to configure.
  
- === LocalFileSystem: ===
+ === Local``File``System: ===
   * Status: mature
   * Slow on window boxes
  
- === DbFileSystem: ===
+ === Db``File``System: ===
   * Status: mature
-  * meant to be used in combination with SimpleDbPersistenceManager as repository & workspace file system 
+  * meant to be used in combination with Simple``Db``Persistence``Manager as repository & workspace file system 
  
- === CQFSFileSystem ===
+ === CQFS``File``System ===
   * Status: mature
   * Mysterious configuration options ;)
   * Mysterious proprietary binary format ;)