Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Message-ID: <38B1B2A6.9877D9FA@algroup.co.uk>
Date: Mon, 21 Feb 2000 21:48:22 +0000
From: Ben Laurie <ben@algroup.co.uk>
Organization: A.L. Group plc
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: extensions in public URIs [was: RE: Variations on a theme by
 Cocoon]
References: <NCBBKKMPILBOFACAPHDDAEKLDOAA.gerard.van.enk@eo.nl>
 <38AA59C9.8D3298DB@localbar.com> <38AB2C10.6426FB04@algroup.co.uk>
 <38AB3180.DFFCC733@apache.org> <38AB337D.F511CFA1@apache.org>
 <38ABBF32.5AD6D149@algroup.co.uk> <38ABD605.3D9B07D5@apache.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stefano Mazzocchi wrote:
> 
> Ben Laurie wrote:
> >
> > Pierpaolo Fumagalli wrote:
> > >
> > > Stefano Mazzocchi wrote:
> > > >
> > > > Ben Laurie wrote:
> > > > >
> > > > > Y'know, the thing that's worrying me about all this is that Apache
> > > > > already has considerable power to do this kind of matching, [...]
> > > >
> > > > I am worried too.
> > > >
> > > > I do see the overlap and I do see the problems.... probably Cocoon might
> > > > well get merged in Apache 2.1... or even become the next apache using
> > > > tomcat + the protocol native libraries... who knows.
> > > >
> > > > Anyway, don't forget Cocoon is a servlet, thus should not presume
> > > > anything about the running environment.
> > >
> > > I am not really worried... First of all because Cocon 2.0 is completely
> > > abstracted from the web server. It's not even a Servlet anymore (or
> > > better, not only a servlet), so, even if there's some overlap, in our
> > > case that overlap is nedeed...
> > >
> > > And anyway the overlap is just on the matching part... We do all the
> > > translation that apache doesn't do right now (BTW, I know
> > > mod_rewrite)... IMVHO it's a completely different model...
> >
> > The issue is that if I want some particular subset of URLs to be served
> > by a particular Cocoon processing chain, but _also_ have, say,
> > restricted access, I have to ensure that the Cocoon and Apache configs
> > match exactly. This is difficult and risky. The simple fix is to allow
> > (but not require) the sitemap to match on handler (or environment
> > variables, which can also be set in a variety of circumstances in
> > Apache), then the sysadmin can choose which approach to take. If you
> > also (optionally) allow the source file to be the result of Apache doing
> > the URL translation (which is available in the environment), then the
> > problem is solved without compromising the generality of sitemaps.
> 
> Very good point.
> 
> Now the question: you need a mod_cocoon to do that, right? sorry, but
> I'm a total apache ignorant.

No, like I said, you just match on handler or environment - which is
already taken care of in the core Apache machinery.

Cheers,

Ben.

--
SECURE HOSTING AT THE BUNKER! http://www.thebunker.net/hosting.htm

http://www.apache-ssl.org/ben.html

Y19100 no-prize winner!
http://www.ntk.net/index.cgi?back=2000/now0121.txt