Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 64.233.184.237 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=dRkOqokZmh04a8PhlEfPOTJ/DvBXxFX1Tr+NLykb0G8wIUFpser/nF86WfMbjvfGlE
         skIw+4KhrenWnPGYEsqPbtzptpyODWjVrN5ncd5DwyXMt/LQ1GmYMw5HVLviKcMdtxTY
         MpWXOHNt/slHF5LVE+qHexmK5+vlJcPNtR2nM=
Message-ID: <510143ac0806170613h21832ce7j6ffdb438a606fd0a@mail.gmail.com>
Date: Tue, 17 Jun 2008 16:13:04 +0300
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Re: RMI vs. JNDI
In-Reply-To: <17898756.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <17876722.post@talk.nabble.com>
	 <c3ac3bad0806170055k4458eedg5a0a9a7eb120a1a3@mail.gmail.com>
	 <17891000.post@talk.nabble.com>
	 <c3ac3bad0806170508o4bf84c70h9801f27055a483cd@mail.gmail.com>
	 <17898756.post@talk.nabble.com>

Hi,

On Tue, Jun 17, 2008 at 3:57 PM, krisNog <kris.glover@bluenog.com> wrote:
> What I really need to find out is what sort of latency there is when using
> RMI to make calls to the JCR API.

Most JCR-RMI calls are remote, so you'll have the overhead of a
network roundtrip per each method call.

There's been some discussion about avoiding so many network roundtrips
by pre-fetching or caching content on the client side, but so far such
improvements have only been implemented for some simple cases like
RangeIterator.next().

BR,

Jukka Zitting