Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 26877 invoked by uid 500); 8 Jan 2003 15:57:19 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 26865 invoked from network); 8 Jan 2003 15:57:18 -0000 X-Authentication-Warning: vern.chem.tu-berlin.de: stephan owned process doing -bs Date: Wed, 8 Jan 2003 16:57:19 +0100 (CET) From: Stephan Michels X-X-Sender: stephan@vern.chem.tu-berlin.de To: cocoon-dev@xml.apache.org Subject: Re: Defining Source Interfaces In-Reply-To: <3E1C4731.7010007@anyware-tech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, 8 Jan 2003, Sylvain Wallez wrote: > >Anyway, I think your arguments are better than mine (sniff). > > > >So, we have a TraversableSource or HierarchicalSource or ...? > > I'm not a native speaker, but the definition of traversable given by > dictionary.com makes me prefer hierarchical... You could traverse the hierarchy ;-) > Ah, and what about adding an "exists()" method on Source (it's currently > on WriteableSource) ? That one makes sense and is really useful, as the > current way to know if an URI exists is to try to getInputStream(), > which can be heavy. +1 > About the move() and copy() methods, I don't know if they should be kept > in the new incarnation of this interface. :-/ not another MoveableSource ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org