Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 95911 invoked from network); 18 Jun 2000 09:24:00 -0000 Received: from rubel.maz.org (209.60.53.26) by locus.apache.org with SMTP; 18 Jun 2000 09:24:00 -0000 Received: (qmail 31706 invoked by uid 500); 18 Jun 2000 09:24:25 -0000 Date: Sun, 18 Jun 2000 02:24:25 -0700 (PDT) From: brian moseley X-Sender: bcm@rubel.maz.org To: cocoon-dev@xml.apache.org cc: Andrew Savory Subject: Re: sitemap draft still needs work in the matcher/chooser area In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Sat, 17 Jun 2000, Donald Ball wrote: > Is mapping URLspace to filespace really cocoon's job? > That's traditionally the job of a web server as well. only when it's really just serving files. cocoon doesn't limit itself thus. > Since we're carving out URLspace in the cocoon sitemap, > doesn't it make sense to at least offer the option to > have access to the various URLs limited in the sitemap? > Read over the current sitemap working draft and see if > you're still in disagreement. i go back and forth on this issue, but currently i think authentication and authorization should be managed by the environment, not by the content production engine. the intersection of the two should only ever be in configuration.