Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 35287 invoked from network); 25 Nov 2004 10:12:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 25 Nov 2004 10:12:08 -0000 Received: (qmail 93231 invoked by uid 500); 25 Nov 2004 10:11:48 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 93137 invoked by uid 500); 25 Nov 2004 10:11:47 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 93114 invoked by uid 99); 25 Nov 2004 10:11:46 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of oliver.zeigermann@gmail.com designates 64.233.184.203 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.203) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 25 Nov 2004 02:11:44 -0800 Received: by wproxy.gmail.com with SMTP id 55so185805wri for ; Thu, 25 Nov 2004 02:11:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=VseTrWxx2YJh+AWSbyqGD1io7yQz3YlWc73pJWq/ompypwdOEpt4qNJGFgyjsfIjZ+ibK5fCSuLsHncNKfnqXZLopXkmd2rqjv82P9ZNtTQ15+57z2QJniDQsVtM7nf03Diz2B8O6WYRCd59GJTFbt3GGsf91K4IGiJ8cRPP0w8= Received: by 10.54.25.38 with SMTP id 38mr156859wry; Thu, 25 Nov 2004 02:11:41 -0800 (PST) Received: by 10.54.11.53 with HTTP; Thu, 25 Nov 2004 02:11:41 -0800 (PST) Message-ID: <9da4f45204112502116e1d5bd2@mail.gmail.com> Date: Thu, 25 Nov 2004 11:11:41 +0100 From: Oliver Zeigermann Reply-To: ozeigermann@apache.org To: Jakarta Commons Users List Subject: Re: [vfs] webdav checkin checkout lock unlock In-Reply-To: <41A4C229.5020709@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1391069965@web.de> <41A4C229.5020709@apache.org> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Wed, 24 Nov 2004 18:17:29 +0100, Mario Ivankovits wrote: > Daniel Florey wrote: > > >I'd recommend to clearify the scope of [vfs]. > >Is it supposed to be a very simple api to access different file systems? > >Or is the scope larger so that we want to have abilities to manage distributed authoring (locks), versioning and searching? > >If it would be the latter, I think we'll conflict with many other projects that aim this target (Jackrabbit, Slide...) > >My personal favorite in this area is WebDAV as it adressess all of this requirements in the most mature way (but unfortunately there is currently no Java API reflecting the whole WebDAV-stuff in a simple and intuitive way). > >My suggestion would be to keep it very simple and implement only things that fit into the first scope. > > > > > I am with you if you talk about the checkout/checkin functionality. > > But I think locking is something a filesystem should be able to handle > to - and then as always - if the underlaying filesystem supports this > VFS should dispatch such requests down to the filesystem. I guess it is pretty hard to draw the line somewhere, as some file systems even support versioning. What about access rights, is it supported by VFS? Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org