On 04/07/2017 11:48, Julian Sedding wrote: > A much more important and difficult question to answer IMHO is how to > deal with the slow retrieval of archived content. And if needed, how > to expose the slow availability (i.e. unavailable now but available > later) to the end user (or application layer). To me this sounds > tricky if we want to stick to the JCR API.
I think we should NOT touch the JCR api but rather use/expose the Oak API for such features. And having a consuming application leverage one, the other or both. If we are going to touch the JCR API we should probably sit down a while and think about JCR API 3 ;) Davide
