On Thu, Jul 19, 2012 at 10:18 AM, Stefan Guggisberg
implementing the transient space in Oak-Core is
legitimate, although premature optimization for
the specific use case where the entire stack
(jcr-...-mk) runs in the same vm.
To clarify, the decision to write changes from oak-jcr directly to
oak-core was not driven by performance ("premature optimization") but
rather by the need a) to in any case have those changes in oak-core
for validation, etc. and c) to support large content imports that
wouldn't necessarily fit into memory. We also wanted to avoid having
to write essentially the same code twice for oak-core and oak-jcr. The
performance benefit of reduced amount of internal copying and memory
overhead is just a nice side-effect of the design.
See the mentioned list archives of March/April for more background,
with ,  and  being good starting points.