Return-Path: 
 <cocoon-dev-return-25299-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 32550 invoked by uid 500); 8 Apr 2002 11:01:53 -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 32539 invoked from network); 8 Apr 2002 11:01:52 -0000
X-Antivirus-Data: Virus data file v4189 created Mar 06 2002
Message-ID: <3CB17552.1F287B66@apache.org>
Date: Mon, 08 Apr 2002 12:47:46 +0200
From: Stefano Mazzocchi <stefano@apache.org>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Serializer configuration, was: [status & RT] design challenges
References: <007501c1dd23$c824e6e0$9274558b@vgritsenkopc>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Vadim Gritsenko wrote:
> 
> > From: Sylvain Wallez [mailto:sylvain.wallez@anyware-tech.com]
> >
> > Stefano Mazzocchi wrote:
> 
> <skip/>
> 
> > > 1) serializers don't have full access to the component environment
> > > and some want this to be changed
> > >
> >
> > The major need is to be able to access the SourceResolver. I haven't
> > seen any good use case where a Serializer needs to access something
> else
> > in the environment.
> 
> Many of the Cocoon components accept configuration when declared in the
> components part of the sitemap. Examples:
> TraxTransformer:
>   <use-request-parameters>false</use-request-parameters>
> I18nTransformer:
>   <catalogue-name>messages</catalogue-name>
> HTMLSerializer:
>   <buffer-size>1024</buffer-size>
> SVGSerializer:
>   <parameter name="quality" type="float" value="0.9"/>
> 
> All of these components (with one exception) allow overriding global
> defaults at the moment of component usage:
> 
> TraxTransformer:
>   <map:parameter name="use-request-parameters" value="false"/>
> I18nTransformer:
>   <map:parameter name="catalogue-name" value="messages"/>
> 
> Now you can guess the exception: serializers. They are the only
> components which do not allow overriding defaults.
> 
> The question is where the error in design is. Is it in allowing
> serializer to have a configuration or in disabling the ability to
> override this configuration?

Good point, I agree this is an unnecessary drawback.

Ok, listen: if enough people whan this to change, maybe it's time to do
it.

I think you and Sylvain know more about the internals of the pipelines
that I do, so I'll turn my votes on the serializers to -0 and trust you
guys.

Just one think: keep caching concerns *very* clear in mind.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



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