Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 54322 invoked by uid 500); 16 Dec 2002 15:24:37 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 54310 invoked from network); 16 Dec 2002 15:24:36 -0000 Received: from eos.telenet-ops.be (195.130.132.40) by daedalus.apache.org with SMTP; 16 Dec 2002 15:24:36 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by eos.telenet-ops.be (Postfix) with SMTP id 12130212F7 for ; Mon, 16 Dec 2002 16:24:38 +0100 (CET) Received: from outerthought.org (D5E00A87.kabel.telenet.be [213.224.10.135]) by eos.telenet-ops.be (Postfix) with ESMTP id E27AA20CAA for ; Mon, 16 Dec 2002 16:24:37 +0100 (CET) Message-ID: <3DFDF035.3050401@outerthought.org> Date: Mon, 16 Dec 2002 16:24:37 +0100 From: Steven Noels Organization: Outerthought User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: File prefix again (Re: Cocoon CLI - how to generate the whole site) References: <3DF8BDFF.9060109@apache.org> <20021213135011.GF390@expresso.localdomain> <3DF9F7C9.4020604@apache.org> <20021213160934.GA7718@expresso.localdomain> <3DFA0B7F.6050006@apache.org> <20021213170618.GC7718@expresso.localdomain> <20021216055750.GB1708@expresso.localdomain> <3DFD87E4.1090508@apache.org> <20021216120309.GA2355@expresso.localdomain> <3DFDCEC0.1060109@apache.org> <20021216142017.GC2355@expresso.localdomain> <3DFDEC75.1020700@apache.org> In-Reply-To: <3DFDEC75.1020700@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Nicola Ken Barozzi wrote: > Jeff Turner wrote: >> Having to interrogate the filesystem to decide a URI's scheme is a >> total hack. >> What happens if our docs are stored in Xindice, or anything other than a >> filesystem? Resource-exists is going to break. > Hmmm, this is a good point, but not a resource-exists "conceptual" > problem. I can test if a resource exists also in remote repositories. > If the "file:" thing takes care different backends, there is no reason > why a better resource-exists cannot. So seems is more about the > deficiencies of the resource-exists implementation rather than the need > of a site: scheme. The way resource-exist was brought into Forrest was based on a hackish idea. The way it works is a hack. I like the file: approach much better, and I don't feel like I don't understand Cocoon or anything else because of that. It's on the same level of letting the user put hints in his documents as we currently inform people about some obscure XLink attribute which can be set to stop crawling. At the very least, file: will have been designed & coded by a community. -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://radio.weblogs.com/0103539/ stevenn at outerthought.org stevenn at apache.org