jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig <mdue...@apache.org>
Subject Re: Securing Workspace#copy
Date Wed, 05 Feb 2014 19:56:18 GMT


On 5.2.14 7:49 , Angela Schreiber wrote:
> hi jukka
>
> i can live with that as well.... what do others think?
>
> kind regards
> angela
>

If we can live without Tree.copy, yes I think this is a good idea.

Michael

> On 05/02/14 19:35, "Jukka Zitting" <jukka.zitting@gmail.com> wrote:
>
>> Hi,
>>
>> On Wed, Feb 5, 2014 at 1:19 PM, Angela Schreiber <anchela@adobe.com>
>> wrote:
>>> would we in this case still have the need for Root#copy?
>>> wouldn't it be better then to just drop that and build
>>> Workspace#copy in oak-jcr altogether?
>>
>> That would make sense, yes.
>>
>> The only case I can see for not doing this would be having an
>> Oak-based non-JCR repository that doesn't need to worry about things
>> like access control, versioning or locking. Such a repository could
>> benefit from a copy-by-reference operation, but for now I'd be happy
>> to drop the feature at the Oak level and only restore it if/when a new
>> use case comes along.
>>
>> BR,
>>
>> Jukka Zitting
>

Mime
View raw message