Hi Jukka, Thanks - this is very helpful context. If I read the issue correctly then a) the use case was already requested back then and b) random writes did not make it into the spec at least partly because some backing implementations would have struggled to implement it.
I think it makes a lot of sense to re-visit this feature as part of the broader list of use cases for efficiently handling binaries that Chetan was kind enough to compile. Especially, if this extension is implemented specifically for Oak then the considerations on different backing impls would be much simplified. Cheers Michael On 02/06/16 17:02, "Jukka Zitting" <jukka.zitt...@gmail.com> wrote: >Hi, > >See https://java.net/jira/browse/JSR_283-19 for more background on the >decision to not have this feature in JCR 2.0. > >That said, I remember this feature request coming up every now and then, >and we did for example design handling binary values in the segment store >in a way that would allow random write access to be implemented efficiently >if there's enough demand. > >Best, > >Jukka Zitting > > >On Thu, Jun 2, 2016 at 10:25 AM Michael Marth <mma...@adobe.com> wrote: > >> >> > >> >...but the limitation is also present in the JCR API, right? >> >> yes, that is my understanding >>
