Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 97439 invoked from network); 10 Feb 2010 14:17:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Feb 2010 14:17:19 -0000 Received: (qmail 786 invoked by uid 500); 10 Feb 2010 14:17:19 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 721 invoked by uid 500); 10 Feb 2010 14:17:19 -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 713 invoked by uid 99); 10 Feb 2010 14:17:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Feb 2010 14:17:19 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aklimets@day.com designates 207.126.148.88 as permitted sender) Received: from [207.126.148.88] (HELO eu3sys201aog102.obsmtp.com) (207.126.148.88) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 10 Feb 2010 14:17:11 +0000 Received: from source ([209.85.220.216]) by eu3sys201aob102.postini.com ([207.126.154.11]) with SMTP ID DSNKS3K/zv6Izlh75tZ7SkEIxhDqA1uDy8RI@postini.com; Wed, 10 Feb 2010 14:16:50 UTC Received: by fxm8 with SMTP id 8so47862fxm.6 for ; Wed, 10 Feb 2010 06:16:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.4.145 with SMTP id 17mr403055far.17.1265811406036; Wed, 10 Feb 2010 06:16:46 -0800 (PST) In-Reply-To: References: <510143ac1002090755l32715557p7ae8f841cbb53853@mail.gmail.com> Date: Wed, 10 Feb 2010 15:16:45 +0100 Message-ID: Subject: Re: Jackrabbit 3: repository requirements From: Alexander Klimetschek To: dev@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 9, 2010 at 23:04, Guo Du wrote: > Architecture for modular design > * Other way to configure repository than repository.xml. See https://issues.apache.org/jira/browse/JCR-1438 > * Get implementation/resource/service from OSGi environment There is some stuff happening wrt to LoginModules in Sling. And it should be done alongside JCR-1438. I added a note to the bug. > Scalability > * Scale to complexity. Add graph style operation, e.g. a blog post may > have multiple path to retrieve: date, author, tag. Did you look at shareable nodes in JCR 2.0? I think Jackrabbit should be careful and not add new API-level features that are not standardized. > Connector interface to other system > * Expose other system via jcr api. e.g. S3, google, source control system. This is something for which jcr spi is intended for. The jcr2spi provides the transient client implementation and you "only" have to implement the simpler spi interface. Also, via spi a lot of common stuff (node type templates, namespace parsing, etc.) is already available to simplify implementation from scratch. I don't think this is necessarily important for jackrabbit core. Regards, Alex -- Alexander Klimetschek alexander.klimetschek@day.com