Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 68919 invoked from network); 10 Apr 2006 13:07:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Apr 2006 13:07:21 -0000 Received: (qmail 43188 invoked by uid 500); 10 Apr 2006 13:07:19 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 42915 invoked by uid 500); 10 Apr 2006 13:07:17 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 42756 invoked by uid 99); 10 Apr 2006 13:07:17 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Apr 2006 06:07:17 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of michael.f.watson@gmail.com designates 64.233.184.235 as permitted sender) Received: from [64.233.184.235] (HELO wproxy.gmail.com) (64.233.184.235) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Apr 2006 06:07:16 -0700 Received: by wproxy.gmail.com with SMTP id i3so751498wra for ; Mon, 10 Apr 2006 06:06:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=FuSWYZ21glRYXf2alhPkmRCzLE6xOIRvsZybjfNoB624oXO7ySDXamYDNKMZjrrBR4oJ8ydCqyMqfC+lNCvWpg4lk6g3vlweq/j9qYo4nPf6aFAYMz9DEGnu5RxbRl/D/0iQns7kQzRGVDXZ0kvvktAuY5TCBQCVYUM2YXkswF8= Received: by 10.65.177.14 with SMTP id e14mr804160qbp; Mon, 10 Apr 2006 06:06:55 -0700 (PDT) Received: by 10.65.155.6 with HTTP; Mon, 10 Apr 2006 06:06:55 -0700 (PDT) Message-ID: <7675ea080604100606w383d520ah75e83fbae192226@mail.gmail.com> Date: Mon, 10 Apr 2006 14:06:55 +0100 From: "Mike Watson" To: users@jackrabbit.apache.org Subject: Clustering ETA In-Reply-To: <7675ea080604100603i4b25ecefgd74f86c98ecaf7b0@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2158_521969.1144674415602" References: <7675ea080604100603i4b25ecefgd74f86c98ecaf7b0@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_2158_521969.1144674415602 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Is there a timeline on how far away clustering support is (JCR-169)? The ability to have a clustered application sharing a central jackrabbit repository is a crucial requirement for an application I'm working on. Can someone tell me what the current options are? Is the JCR-RMI option really useable with this warning: "The current JCR-RMI library is designed for simplicity, not performance. You will probably experience major performance issues if you try running an= y non-trivial applications on top of JCR-RMI." ??? Thanks in advance for any info. Regards, Mike ------=_Part_2158_521969.1144674415602--