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)
Importance: normal
Priority: normal
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Subject: RE: remote JCR
Date: Mon, 4 Jan 2010 15:35:24 -0500
Message-ID: 
 <399DA4AB3471814AA1A85085EC6B4E33046BE2F3@nasa-dtw-ex005.nasa.cpwr.corp>
In-Reply-To: <1262358562.2545.26.camel@fitz-hume>
Thread-Topic: remote JCR
Thread-Index: AcqK9HvIv+vshf0lQ+meaN+3tGjrwgCiKLsQ
References: <1262358562.2545.26.camel@fitz-hume>
From: "Hyaduck, John" <John.Hyaduck@compuware.com>
To: <users@jackrabbit.apache.org>

We have been testing JCROM over http to WebDAV (jcr2spi, spi2dav) and =
the lower level functions (locking, etc.) seem to work alright.   The =
JCR API gets translated to SPI html commands that WebDAV then processes. =
 Anyone else experimenting with this? =20


The contents of this e-mail are intended for the named addressee only. =
It contains information that may be confidential. Unless you are the =
named addressee or an authorized designee, you may not copy or use it, =
or disclose it to anyone else. If you received it in error please notify =
us immediately and then destroy it.

From: Mat Lowery [mailto:mlowery@pentaho.com]=20
Sent: Friday, January 01, 2010 10:09 AM
To: users@jackrabbit.apache.org
Subject: remote JCR

I'm trying to wrap my head around Deployment Model 3: Repository Server.
Can anyone confirm that my understanding is accurate?  My understanding
is that there are two ways to access a repository remotely: RMI and
WebDAV.  If you want to use the JCR API, you use RMI.  Otherwise you use
WebDAV.  But by using WebDAV, you lose access to the low level node
operations that you would otherwise have access to in the JCR API.

Let's assume that I need access to the low level node operations.  So I
opt for RMI.

However, there is a statement on
http://jackrabbit.apache.org/repository-server-howto.html that says:

"Warning: The current JCR-RMI library is designed for simplicity, not
performance. You will probably experience major performance issues if
you try running any non-trivial applications on top of JCR-RMI."

Does performance suffer because each and every node operation (e.g.
addNode and setProperty) involves a communication with the server?

In this case, it seems that the best option is to expose my own service
(backed by a local Jackrabbit) for remote access.  In this way, there is
far less communication with the remote service (i.e. my service) since
my objects would be far less granular than nodes.

This is probably obvious to most but it took me a while to figure it out
what my options were.  Can anyone comment?  Thank you.