zopyx.versioning - A MongoDB based versioning solution for Zope and Plone
ZOPYX offering an extended versioning mechanism for Zope and Plone-based applications on top of the no-SQL database MongoDB
ZOPYX brings versioning of contents in Zope and Plone-based applications to a new world.
The traditional versioning mechanism based on CMFEditions has several problems that we solved in a generic and flexibel way with our solution zopyx.versioning:
Highlights:
- pluggable and extensible architecture
- supports versioning of individual content objects or object collections like folders
- individual control over data to be versioned on a per-content-type basis
- flexible versioning policies implementable for object collections (e.g. for a folder (flat or nested)
- purging of individual content revisions
- uses MongoDB as primary versioning storage (support for other database (e.g. ZODB) through adapters)
- optional support for scalability and replication
Highlights of the Plone integration layer:
- supports all Archetypes-based content-types out of the box (except for binary content (image fields and file fileds))
- optional support Dexterity or zope.schema based content
- Plone-integrated revision browser
- field-based diff between revisions
- a revision of a piece of content can be either restored completely or with a user-selectable subset of fields
We intend to release the first production-stable release of zopyx.versioning by October 2010.
A preview of zopyx.versioning will be given at the DZUG conference in Dresden and perhaps at the Plone conference in Bristol this fall.
