Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Thu, 3 Jul 2008 07:57:24 -0700 (MST)
From: Lennard Fuller <lfuller@unicon.net>
To: users@jackrabbit.apache.org
Message-ID: <20633204.132191215097044665.JavaMail.root@zimbra.unicon.net>
In-Reply-To: <18260175.post@talk.nabble.com>
Subject: Re: jcr2spi<->spi-rmi<->spi2jcr<->jackrabbit-core config?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Thanks!  Hopefully I'll have a chance to give this a spin today.  If I come across anything interesting or noteworthy concerning the set up I'll send it Scott's way for possible inclusion in the wiki.  If this method proves to be notably more performant, even in its unoptimized state, I'll post those findings to the mailing list.

Thanks again for your timely responses,
Lennard


----- Original Message -----
From: "scytacki" <scytacki@fastmail.fm>
To: users@jackrabbit.apache.org
Sent: Thursday, July 3, 2008 7:44:16 AM GMT -07:00 U.S. Mountain Time (Arizona)
Subject: Re: jcr2spi<->spi-rmi<->spi2jcr<->jackrabbit-core config?


I created this page which documents how I set things up:
http://wiki.apache.org/jackrabbit/HowtoSpi2Rmi

Angela, I added your comments to that page.


lennard wrote:
> 
> I happened across Jukka Zitting's web page in which he announced some of
> the new features in Jackrabbit 1.4.  In particular, this paragraph was of
> interest.
> 
> "Service provider interface for JCR. The jackrabbit-spi component defines
> an architectural layer below the JCR API. The SPI layer is designed
> specifically for remote access and outlines a way for us to avoid the
> performance limitations of JCR-RMI that works on top of JCR."
> 
> This is because I have JCR client applications which are currently
> accessing the JCR via JCR-RMI.  With a significant amount of client side
> caching the performance is acceptable for our current usage... but only
> just.  The prospect of accessing the JCR external to that JCR's JVM in a
> reasonably performant fashion is very exciting.
> 
> Looking at the mailing list I can see references to a method of getting
> remote access to a JCR using SPI and RMI.
> 
> Marcel mentioned the following alternative:
> jcr2spi<->spi-rmi<->spi2jcr<->jackrabbit-core 
> 
> Thus far I have been unable to find any How to, Readme or wiki page which
> covers this particular configuration.  Can someone point me in the right
> direction?  Is there another configuration I should consider first?
> 
> Lennard Fuller
> Software Architect
> Unicon Inc.
> 
> 

-- 
View this message in context: http://www.nabble.com/jcr2spi%3C-%3Espi-rmi%3C-%3Espi2jcr%3C-%3Ejackrabbit-core-config--tp18248099p18260175.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.