Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 16803 invoked by uid 500); 1 Jun 2002 19:18:49 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 16783 invoked from network); 1 Jun 2002 19:18:48 -0000 Message-ID: <003701c209a0$b7e23db0$96320a3e@PC103> From: "Nicola Ken Barozzi" To: References: <3CF5EBA6.3070405@anyware-tech.com> <3CF626BC.43C4C3E4@apache.org> <3CF63A48.6060606@anyware-tech.com> <003e01c207ea$dd785df0$670004c0@PC103> <3CF7EC35.175D6B1C@apache.org> Subject: Re: [VOTE] Syntax for module-based sitemap variables Date: Sat, 1 Jun 2002 21:15:39 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N From: "Stefano Mazzocchi" > Nicola Ken Barozzi wrote: > > > I still prefer this uri syntax: > > > > {foo} (default sitemap module ) > > {pathto/foo} (default sitemap module with path) > > {module:request://pathto/foo} (complete parameter uri) > > or > > {parameter://request.module/pathto/foo} (complete parameter uri) > > Yes, that's complete, but I question it's effectiveness: all my FS > alarms went on after reading this :/ ;-) Ok, so it would be like this? sitemap params: param or sitemap:param from a module (example): request:param pathed sitemap params: ../../1 Hmmm... I'm puzzeled over the pathed param, and using a URI was the most obvious and consistent way I could find... but URI schemes can be made in different ways... How should handle (generally skeaking, not only 'bout naming) pathed params? :-? -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org