Would it be useful to have a document that starts detailing sections that are
missing in ZODB/ZEO programming guide?

  - Blobs are not mentioned.
  - ZEO/Persistent disk cache not mentioned
  - xdb reference safetybelt
  - Documentation of various backend storages
    - Relstorage, Demostorage, Filestorage
  - MVCC is not mentioned
  - Persistence cache not described
  - savepoints vs. nested transaction
  - Diagnostic recipes (how to diagnosis your application)
  - Known Limitations

How do you guys suggest we work on documentation?
Would it be useful to come up with an outline of the target
documentation?  Then people could start filling in some details.

Maybe Jim could then review instead of produce the documentation?

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -  ZODB-Dev@zope.org

Reply via email to