Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of anchela@adobe.com designates
 64.18.1.29 as permitted sender)
Message-ID: <50741032.4050706@adobe.com>
Date: Tue, 9 Oct 2012 13:53:22 +0200
From: Angela Schreiber <anchela@adobe.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
 rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: <oak-dev@jackrabbit.apache.org>
Subject: Re: [NEWS] Oak new of the week (4th edition)
References: <5073FFB4.6010405@apache.org>
In-Reply-To: <5073FFB4.6010405@apache.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit


> - Finally, there was quite a lot going on in the security area wrt.
> access control, authentication support, principal management and so.
> Angela, since you were mainly concerned with this, do you mind to give a
> quick update on what's new here?

there is just one topic that IMO is worth discussing here:

i think we have a major performance issue with
ContentSession#getLatestRoot that makes the creation of a new
Session really expensive, while i would expect it to be for free.

just came across this again when i wanted to replace the fake
login by what will be the default setup in an oak-repo and
will validate credentials against information stored in the MK
without sharing a 'session' between different repo-logins as
this was/is one of the pain points in jr2.

regards
angela