On Thu, Jul 19, 2012 at 11:26 AM, Stefan Guggisberg
a) in scenarios where the Oak-API is remoted we'll have to buffer transient
changes on the client and batch-write them to the 'server' (Oak-API impl).
handling the transient space exclusively below the Oak-API is IMO not
an option for this use case.
Yes, as I mentioned earlier, that use case calls for batching. Patches welcome.
c) (or rather b) ?) large content imports should IMO be done through
javax.jcr.Workspace#import. there's an equivalent functionality in
the old SPI and it should IMO be exposed in Oak-API as well.