jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bart van der Schans <b.vandersch...@onehippo.com>
Subject Re: NodeStates and security (Re: svn commit: r1458234 - in /jackrabbit/oak/trunk: oak-core/src/main/java/org/apache/jackrabbit/oak/core/ oak-core/src/main/java/org/apache/jackrabbit/oak/kernel/ oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/v...
Date Wed, 20 Mar 2013 13:01:06 GMT
On Wed, Mar 20, 2013 at 12:42 PM, Angela Schreiber <anchela@adobe.com> wrote:
> On 3/20/13 12:34 PM, Bart van der Schans wrote:
>> On Wed, Mar 20, 2013 at 11:24 AM, Jukka Zitting<jukka.zitting@gmail.com>
>> wrote:
>>> The only complication there, as already discussed before, is the
>>> inability of the current NodeState interface to handle cases where a
>>> child node is readable even if its parent is not.
>> This is a quite problematic use-case.
> as a matter of fact we at adobe have to support this use case for
> our products which are the main driver and sponsor for this oak rewrite
> effort.

Well that reduces the question to just *how* to do it ;-)

I was just jumping in because we experienced many problems with this
use case with JR2 and was wondering if it's was worth the effort to
support it.


View raw message