Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 32967 invoked from network); 4 Feb 2004 14:56:39 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Feb 2004 14:56:39 -0000 Received: (qmail 28653 invoked by uid 500); 4 Feb 2004 14:56:26 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 28603 invoked by uid 500); 4 Feb 2004 14:56:25 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 28542 invoked from network); 4 Feb 2004 14:56:24 -0000 Received: from unknown (HELO mail.s-und-n.de) (212.8.217.2) by daedalus.apache.org with SMTP; 4 Feb 2004 14:56:24 -0000 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id DA34719F5AF for ; Wed, 4 Feb 2004 15:56:25 +0100 (CET) Received: from hw0386 ([10.10.2.42]) by notes.sundn.de (Lotus Domino Release 6.5) with SMTP id 2004020415521406-14008 ; Wed, 4 Feb 2004 15:52:14 +0100 From: "Carsten Ziegeler" To: Subject: RE: variable substitution in @type attributes Date: Wed, 4 Feb 2004 15:58:06 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 04.02.2004 15:52:14, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 04.02.2004 15:52:15, Serialize complete at 04.02.2004 15:52:15 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I think one major point is security or more precise: to detect possible problems early on. If you now use a wrong type information, which means address a component that doesn't exist, you get an exception immediately on startup. So, you know very early that your application is not correct. With a dynamic type attribute you defer this to a much later point which might be dangerous as well and very hard to find. Carsten > -----Original Message----- > From: news [mailto:news@sea.gmane.org]On Behalf Of Jorg Heymans > Sent: Wednesday, February 04, 2004 3:51 PM > To: dev@cocoon.apache.org > Subject: Re: variable substitution in @type attributes > > > Vadim, that post is from 2001. > > The arguments are: > - it affects the cache ->is this still relevant for the rewritten cache > mechanism in 2.1+ ? > - Flexibility syndrome ->point taken > - It's a reactor pattern forcing distribution of control and increasing > the number of contracts between the different contexts. ->not sure what > is meant there. Does he mean that selecting a component during pipeline > setup would not be the sole decision of the sitemap anymore? Which > contexts are meant here? > > I can understand the pipeline overhead in looking through the list of > all components everytime for one that matches the parameter, but this > could be documented and left to the user to decide what he prefers most. > > > Please note that I am not trying to advocate this change, just looking > to up my knowledge on cocoon another nudge. > > thanks > Jorg > > Vadim Gritsenko wrote: > > > Jorg Heymans wrote: > > > >> Carrying the discussion over from users@ > >> Why is variable substituion not allowed in @type attributes ? > > > > > > > > Archives have it. > > > > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=98867067826565&w=2 > > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=98867067826565&w=2 > > > > Vadim > > > > > >