Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of julian.reschke@gmx.de designates
 213.165.64.20 as permitted sender)
Message-ID: <4432BB40.6090205@gmx.de>
Date: Tue, 04 Apr 2006 20:30:24 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: dev@jackrabbit.apache.org
Subject: Re: Status of jcr-server
References: <44326BE6.8040200@gmx.de>
 <44327C3F.1080500@day.com>	 <4432A7CF.30008@gmx.de>
	 <29a761a00604041022s5f88515ekc6f757cf8e8d9073@mail.gmail.com>
	 <4432B1F8.4080706@gmx.de>
 <29a761a00604041125t1103ad73u59987c4742976351@mail.gmail.com>
In-Reply-To: <29a761a00604041125t1103ad73u59987c4742976351@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Brian Moseley wrote:
>> I'm still confused. Is this a limitation of the "simple" server, or one
>> of the backends?
> 
> sorry. when i said "back end", i was referring to the "simple server"
> and "jcr remoting server" implementations of the jcr-server
> interfaces.  the implementation of simple server exists in order to
> offer webdav protocol access to a repository full of nt:folder and
> nt:file nodes. it does not offer any other options.

OK, thanks for the clarification.

As far as I can tell this means that neither "jcr-server" (the thingy in 
the "server" subdirectory) nor "simple-server" (the one on the "webapp" 
subdirectory) will act as generic WebDAV servers: one exposes too much, 
the other one too little of the capabilities of JCR.

So is a generic WebDAV server setup that could act as a drop-in 
replacement for things such as Apache/mod_dav, IIS or Slide in scope of 
this Apache activity, or would I need to start my own project for that? 
(Understanding that Cosmo may be part of the answer :-)

Best regards, Julian