Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 42977 invoked by uid 500); 3 Mar 2003 15:33:30 -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 42924 invoked from network); 3 Mar 2003 15:33:29 -0000 Received: from dobit2.rug.ac.be (157.193.42.8) by daedalus.apache.org with SMTP; 3 Mar 2003 15:33:29 -0000 Received: from allserv.rug.ac.be (allserv.rug.ac.be [157.193.40.42]) by dobit2.rug.ac.be (8.11.1/8.11.1) with ESMTP id h23FXUZ29666 for ; Mon, 3 Mar 2003 16:33:30 +0100 (MET) Received: from otsrv1.iic.rug.ac.be (otsrv1.iic.rug.ac.be [157.193.121.51]) by allserv.rug.ac.be (8.11.1/8.11.1) with ESMTP id h23FXTB02091 for ; Mon, 3 Mar 2003 16:33:29 +0100 (MET) Received: from outerthought.org (host104 [192.168.123.104]) by otsrv1.iic.rug.ac.be (8.11.6/8.11.6) with ESMTP id h23FXT525259 for ; Mon, 3 Mar 2003 16:33:29 +0100 Message-ID: <3E6375C9.905@outerthought.org> Date: Mon, 03 Mar 2003 16:33:29 +0100 From: Steven Noels Organization: Outerthought User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: [RT] Dynamic sitemaps References: <20030228122712.GA6105@expresso.localdomain> In-Reply-To: <20030228122712.GA6105@expresso.localdomain> 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 Jeff Turner wrote: > I once thought auto-mounted sub-sitemaps could allow us to break up the > sitemap, but I'm rather skeptical now. Once a request is delegated to a > subsitemap, it *has* to be handled in that subsitemap. We can't > speculatively throw in a . I haven't spend much thinking on this, but couldn't this bad behaviour be caused by the fact we usually map:mount specific 'subdirectories' in our URI space: match pattern="foo/**" mount src="mountables/{1}" uri-prefix="mounted/{1}" Now if we change the thinking to mounting specific media types instead, would that help? : match pattern="**.*" mount src="mountablecontenttypes/{2}" uri-prefix=" " ^ don't know what to put in here ---------------------| so that requests for URI = foo/bar/resourcename.mediatype are routed to the sitemap responsible for producing the relevant response for that media type. Of course, this brings the discussion back (gee!) of Marc's infamous double extensions, which I strongly despise. Also, I don't know whether this will offer more robustness to the mount concept, nor any enhanced modularity. It was just something that came across my mind when reading your mails. I have the tendency to agree with your problem statement, but clearly it is one of these border scenarios again, just like reverting the sitemap and the link rewriting thing. Hm. -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org