Return-Path: 
 <cocoon-dev-return-28750-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 53577 invoked by uid 500); 27 Jun 2002 12:34:12 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 53551 invoked from network); 27 Jun 2002 12:34:12 -0000
From: "Vadim Gritsenko" <vadim.gritsenko@verizon.net>
To: <cocoon-dev@xml.apache.org>
Subject: RE: [RT]: Unifying input modules and global parameters
Date: Thu, 27 Jun 2002 08:33:30 -0400
Message-ID: <00f601c21dd6$d81f4510$0a00a8c0@vgritsenkopc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
In-Reply-To: <GMEBIBHGAOFGJCDPJANDMEALELAA.cziegeler@s-und-n.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N

> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> 
> In the latest CVS of 2.1, I think we have two overlapping
> concepts: the global parameters and the input modules.
> Perhaps we could merge the global parameters somehow into
> the input modules and then remove the global parameters
> as a separate concept again.
> 
> Current State
> -------------
> 
> Currently, the global parameters are declared in the
> map:pipelines section of a sitemap and the scope
> is the map:pipeline sections.
> So, if you want to refer to a global parameter, for
> example named "skin", you have to use
> {skin}, or {../skin} etc. depending on the depth of
> your statement in the map:pipeline section.
> 
> Disadvantages:
> - If you refer to a global parameter, you have to
>   precisly specify the path (= count the ../)
> - global parameters are not inherited/available to
>   sub-sitemaps
> 
> Advantage:
> - Configuration directly in the sitemap
> 
> 
> The input modules are completly defined in the cocoon.xconf,
> they can be used inside every sitemap by first choosing
> the input module and then the key, like {request:parametername}.
> 
> Advantage:
> - Simple use
> - Single configured values are available in all sitemaps
> 
> Disadvantage:
> - Configuration is not in the sitemap, but in the cocoon.xconf
> 
> 
> Proposed Solution
> -----------------
> Make one input module sitemap configurable, like the
> authentication manager. This means a (global) input module is
> defined in the cocoon.xconf, but can be additionally configured
> in the sitemap.
> A subsitemap inherits this configuration from it's parent sitemap
> and can add own key/value pairs, so this would look like this:
> 
> <map:pipelines>
>   <map:component-configurations>
>     <global-input-module>
>       <skin>some-value</skin>
>       ...
>     </global-input-module>
>   </map:component-configurations>
> </map:pipelines>
> 
> So, the key {global:skin} is available in this sitemap and in
> all sub-sitemaps.
> 
> Comments? Suggestions?

+1. Sounds good.

Vadim

 
> Carsten
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org