Hi, >There's no need for the Oak API to reflect JCR in all its details.
Sure. First we need to define how the JCR API implementation is supposed to behave. Based on that we can then still decide what the Oak API should look like. The Oak API is (more or less) an implementation detail. Of course the Oak API support more features, but that's not really relevant for the user of Oak. When I opened OAK-300, it was for the JCR API implementation. If getSize(int max) is just in the Oak API but not available for the end user, then we didn't really gain much :-) Regards, Thomas
