Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 46714 invoked by uid 500); 12 Dec 2002 10:41:08 -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 46523 invoked from network); 12 Dec 2002 10:41:03 -0000 Received: from cmailg1.svr.pol.co.uk (195.92.195.171) by daedalus.apache.org with SMTP; 12 Dec 2002 10:41:03 -0000 Received: from modem-2829.chimpanzee.dialup.pol.co.uk ([217.134.123.13] helo=oxygen.internal.luminas.co.uk) by cmailg1.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 18MQlt-0008Ao-00 for forrest-dev@xml.apache.org; Thu, 12 Dec 2002 10:40:50 +0000 Received: from savs (helo=localhost) by oxygen.internal.luminas.co.uk with local-esmtp (Exim 3.35 #1 (Debian)) id 18MQkD-0004DT-00 for ; Thu, 12 Dec 2002 10:39:05 +0000 Date: Thu, 12 Dec 2002 10:39:05 +0000 (GMT) From: Andrew Savory X-X-Sender: savs@oxygen.internal.luminas.co.uk To: forrest-dev@xml.apache.org Subject: Re: URI spaces: source, processing, result In-Reply-To: <3DF85A4F.6070305@outerthought.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Andrew Savory X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, 12 Dec 2002, Steven Noels wrote: > could you please comment on my summary, too? Also, I'd like to hear the > opinion of others. Ok, caveat: I've not used Forrest (yet), but I use Cocoon extensively. Jeff Turner wrote: > Are you really suggesting that requests for Javadoc pages should go > through Cocoon? > > But the problem is real: how do we integrate Javadocs into > the URI space. > > I'd say write out .htaccess files with mod_rewrite rules, and figure out > what the equivalent for Tomcat is. Perhaps a separate servlet.. > _anything_ but Cocoon ;P Whilst I understand your concern about passing 21mb of files through Cocoon untouched, I'm not sure there's a more elegant way of handling URI space issues, without ending up bundling a massive amount of software with Forrest (or making unrealistic software prerequisite installation demands). So, since Cocoon _can_ handle the rewriting concern, and is already in Forrest, why not use it? I like the idea of link naming schemes, but I'm really worried about the idea of specifying MIME types as link attributes. This seems like a nasty hack: should we be specifying MIME types? Why would we want to know that the PDF I'm linking to is application/pdf? Or even worse, application/pdf+uml? Seems like it would make my job harder. I guess I'd better go track down the arguments in favour of this in the mailing list archive. Andrew. -- Andrew Savory Email: andrew@luminas.co.uk Managing Director Tel: +44 (0)870 741 6658 Luminas Internet Applications Fax: +44 (0)700 598 1135 This is not an official statement or order. Web: www.luminas.co.uk