cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [proposal] some changes toSourceResolver.resolve(baseURI,location, params)
Date Mon, 26 May 2003 12:08:08 GMT
Bruno Dumon wrote:
> >  - so if this can still be kept compatible
> > perhaps by using a "new ExtendedSourceFactory" interface it
> > would be great.
> > 
> > What do you think?
> > 
> 
> Another idea just entered my mind (via marc): what about adding an extra
> set of components to handle relative-to-absolute uri conversion, in
> parallel with the source resolver factories.
> 
> For each scheme, it is then possible to define the relative uri
> resolving strategy to use.
> 
> <uri-absolutizers>
>   <component-instance class="...DefaultAbsolutizer" name="*"/>
>   <component-instance class="...NoAuthorityAbsolutizer" name="cocoon"/>
>   <component-instance class="...NoAuthorityAbsolutizer" name="context"/>
>   <component-instance class="...NotSupportedAbsolutizer" name="mailto"/>
> </uri-absolutizers>
> 
> This would also solve the backwards-incompatibility problem, and
> generally seems like a nicer solution to me.
> 
Hmm, this seems a little bit like overcomponentization to me. It is a 
compatible way, yes, but configuring this is more difficult I think
and if I add a new protocol I have also to add an uri-absolutizer.
I'm just wondering, how many methods there are for uri-absolutizing?

Carsten

Mime
View raw message