Hi, On Tue, Jan 29, 2013 at 1:43 PM, Michael Dürig <mdue...@apache.org> wrote: > Maybe we can even pick up an earlier idea and use the node type information > (i.e. template records here) to optimise how nodes are stored.
That would clearly be useful but I'm a bit hesitant about mixing higher level concerns like node types with the underlying storage model, especially since node types are generally mutable (even the built-in ones changed slightly between JCR 1.0 to 2.0). The template model as described is a more data-driven approach to the same problem. It doesn't reach the level of optimization that could be achieved by making the code understand node types, but on the other hand it deals very well with unstructured nodes that have no hard schema but still follow common patterns. The inspiration for the template idea comes from the way modern JavaScript runtimes generate and use hidden classes for otherwise untyped objects. BR, Jukka Zitting
