Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of julian.reschke@gmx.de
 designates 213.165.64.23 as permitted sender)
Message-ID: <4F2C6214.5050000@gmx.de>
Date: Fri, 03 Feb 2012 23:39:16 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: dev@jackrabbit.apache.org
CC: =?ISO-8859-1?Q?Michael_D=FCrig?= <mduerig@apache.org>
Subject: Re: [jr3 microkernel] Change log consolidation
References: <4F2C2B0E.7050508@apache.org>
In-Reply-To: <4F2C2B0E.7050508@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 2012-02-03 19:44, Michael D�rig wrote:
> ...

Sounds very interesting.

I have a comment that may not even apply to this work, but still: 
recently a JCR issue was opened because Jackrabbit doesn't fire 
compliant NODE_MOVE events for reorder operations. Turns out that 
Jackrabbit doesn't keep sufficient information, and then tries to guess, 
and sometimes guesses wrong.

We should make a conscious decision whether it's important to have this 
information in observation events. Based on that we may want to tune the 
JCR 2.1 spec.

Best regards, Julian