Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2012-03-15 15:24:30 →
Size: 489
Editor: JukkaZitting
Comment: Some graphics about the proposed Oak component structure
← Revision 2 as of 2012-03-15 16:20:30 → ⇥
Size: 1068
Editor: MichaelDürig
Comment: Add notes
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:

Functionality which goes into oak-jcr:
 * Transient space: using Microkernel for write ahead
 * Name space (re-) mapping: use prefix throughout the stack. Either rename or double dispatch on remapping
 * copy, move, import, export
 * UUID resolution

Functionality which goes below the Oak API:
 * Tree update and access
 * Versioning (including mechanism for import)
 * ACL evaluation
 * Authentication
 * Name space map (i.e. the realisation of the map, not the process of (re-) mapping)
 * Name and path validation
 * Locking?
 * UUID map
 * UUID validation

From the oak-dev@ list, here's an early proposal for the overall Oak component structure:

http://people.apache.org/~jukka/2012/oak-components-medium.png

A suggested way of dividing this to actual components (already outdated):

http://people.apache.org/~jukka/2012/oak-components2-medium.png

Whiteboard from a discussion about how the functionality between the JCR and MP APIs should be organized:

http://people.apache.org/~jukka/2012/oak-components3-medium.jpg

Functionality which goes into oak-jcr:

  • Transient space: using Microkernel for write ahead
  • Name space (re-) mapping: use prefix throughout the stack. Either rename or double dispatch on remapping
  • copy, move, import, export
  • UUID resolution

Functionality which goes below the Oak API:

  • Tree update and access
  • Versioning (including mechanism for import)
  • ACL evaluation
  • Authentication
  • Name space map (i.e. the realisation of the map, not the process of (re-) mapping)
  • Name and path validation
  • Locking?
  • UUID map
  • UUID validation

OakComponentStructure (last edited 2012-03-15 16:20:30 by MichaelDürig)