From dev-return-19370-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Tue Jul 15 07:16:40 2008 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 30028 invoked from network); 15 Jul 2008 07:16:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jul 2008 07:16:39 -0000 Received: (qmail 96156 invoked by uid 500); 15 Jul 2008 07:16:38 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 96125 invoked by uid 500); 15 Jul 2008 07:16:38 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 96114 invoked by uid 99); 15 Jul 2008 07:16:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jul 2008 00:16:38 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 15 Jul 2008 07:15:53 +0000 Received: (qmail 29807 invoked from network); 15 Jul 2008 07:16:16 -0000 Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; 15 Jul 2008 07:16:16 -0000 Message-ID: <487C4EBF.1020209@apache.org> Date: Tue, 15 Jul 2008 09:16:15 +0200 From: Carsten Ziegeler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de; rv:1.8.1.14) Gecko/20080421 Lightning/0.8 Thunderbird/2.0.0.14 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: dev@jackrabbit.apache.org Subject: Re: [RT] Adding event interface to jackrabbit api References: <486CCF28.4090301@apache.org> <510143ac0807071614y1f3ae750lc7b34c64e468e776@mail.gmail.com> <48730270.6090500@apache.org> <487B024B.9040909@apache.org> <510143ac0807140137h57a7d931p276ae397f614c113@mail.gmail.com> In-Reply-To: <510143ac0807140137h57a7d931p276ae397f614c113@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Jukka Zitting wrote: > Hi, > > On Mon, Jul 14, 2008 at 10:37 AM, Carsten Ziegeler wrote: >> what is now the prefered way? Extending the event interface or >> providing a marker interface for the event listener? > > Whoever writes the patch gets to decide. :-) > Hehe, right! > The reason I prefer marking the event listener is that it simplifies > the client code a bit and potentially (not currently, but perhaps in > future) allows the repository to optimize event delivery as it has > better knowledge of what events a listener is interested in. But I > wouldn't object to the alternative if you think it's better. > No, I agree with you and Marcel and think that the interface is the nicer way of handling this. The only drawback would be that the implementation is not able to check whether the feature is supported or not; but I guess this could be done by checking the jcr implementation on startup. Carsten -- Carsten Ziegeler cziegeler@apache.org