Return-Path: 
 <dev-return-26600-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
Received: (qmail 56474 invoked from network); 23 Dec 2009 22:37:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 23 Dec 2009 22:37:34 -0000
Received: (qmail 91076 invoked by uid 500); 23 Dec 2009 22:37:34 -0000
Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
Received: (qmail 90997 invoked by uid 500); 23 Dec 2009 22:37:34 -0000
Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:dev@jackrabbit.apache.org>
List-Id: <dev.jackrabbit.apache.org>
Reply-To: dev@jackrabbit.apache.org
Delivered-To: mailing list dev@jackrabbit.apache.org
Received: (qmail 90986 invoked by uid 99); 23 Dec 2009 22:37:34 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2009 22:37:34 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of ehsavoie73@gmail.com designates
 209.85.221.186 as permitted sender)
Received: from [209.85.221.186] (HELO mail-qy0-f186.google.com)
 (209.85.221.186)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2009 22:37:26 +0000
Received: by qyk16 with SMTP id 16so3056440qyk.15
        for <dev@jackrabbit.apache.org>; Wed, 23 Dec 2009 14:37:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type;
        bh=UmapwOSxAmxtG3UPuLx4jeHBep3neCedxLbEfd9f8mY=;
        b=kctsJnqMWVMDLGR00a4IHqzrRUKF2DSPLD9Mw5/cnBq1sVypdedcsm1v1gKUunAIA5
         fJ0WgyyvK2QNNAZpNreRySamwvn2krV6rQ++GcUORtLtONVptuy4dSbsM7GBw2OXfHWR
         cE6b20fW/SxagF1LjE9BiPYmEVJibzi8o31jY=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=Il/M3rJNcbHUL6sJJSYROkJs2Elb1iZNY1rYqKGCE8sKtXvYHtkuFNOxEE4i77kOZA
         sl4m0XN+wZK9wA+6J+rEGDO1qEF0W/iVRZ2bZkaTCxAQwnq0meUjyFJbLn8CaztTKGXy
         650Kc08ajMheRVUYO8stiNwWx1lImxWHa6pQA=
MIME-Version: 1.0
Received: by 10.229.19.149 with SMTP id a21mr317448qcb.29.1261607825140; Wed,
	23 Dec 2009 14:37:05 -0800 (PST)
In-Reply-To: <697f8380912150721u3c8798c5h998308ce9cace44b@mail.gmail.com>
References: <510143ac0910200652k69a5b1dbg9257a61d21d26b00@mail.gmail.com>
	 <697f8380912150721u3c8798c5h998308ce9cace44b@mail.gmail.com>
Date: Wed, 23 Dec 2009 23:37:05 +0100
Message-ID: <84f068130912231437w73c94eben9a876056d4ed027d@mail.gmail.com>
Subject: Re: Remoting and future of JCR-RMI
From: Emmanuel Hugonnet <ehsavoie73@gmail.com>
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=UTF-8
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,
I was porting an eXo JCR shell tool (http://code.google.com/p/crsh/)
to Jackrabbit and this incompatibility as driven me back to 1.6.
Jukka you mentioned  another post : <quote>
At Day we've been increasingly using the spi2dav layer, and except for
being a bit more complicated to set up (see my other post on how to
address that issue) it's already quite usable as a replacement for
JCR-RMI.</quote> I assume it is the JCR-2360 issue, am i right ?

If webdav is the way to get for remote access, could you please give
us some documentation on how to configure the client and server for
this communication ?

Emmanuel

On Tue, Dec 15, 2009 at 4:21 PM, Ard Schrijvers
<a.schrijvers@onehippo.com> wrote:
> Hello Jukka,
>
> On Tue, Oct 20, 2009 at 2:52 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
>>
>> With enough work we could solve both of the above issues to make
>> JCR-RMI work with all combinations of JCR 1.0 and 2.0 clients and
>> servers. However I'm not convinced that it makes sense to spend all
>> that effort when we now have the WebDAV-based remoting layer that's
>> already pretty feature-rich.
>
> I haven't worked with WebDAV since the move of Slide to Jackrabbit,
> but I remember there was no support for DASL before. How do other
> people query a remote repository over WebDAV?
>
> I also used to think that most developers and users that were
> accessing a standalone repository would do so by connecting over RMI
> (or does it happen to be webdav?)...we at Hippo do so during
> development at least, and use embedded repositories in a production
> mode
>
> Regards Ard
>
>>
>> So I'm thinking of putting JCR-RMI on a maintenance track for old 1.x
>> releases, and perhaps even dropping the RMI layer entirely from
>> Jackrabbit 2.0.
>>
>> WDYT?
>>
>> BR,
>>
>> Jukka Zitting
>>
>