forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Scherler <>
Subject Re: Locationmap - because we can doesn't mean we should
Date Wed, 07 Dec 2005 17:40:15 GMT
El mié, 07-12-2005 a las 16:33 +0000, Ross Gardler escribió:


> > In my definition the "cocoon:/" protocol is a source location as any
> > other.
> No, the cocoon: protocol defines which pipeline to use, the locationmap 
> defines the location of the source.

Hmm, a pipeline *is* as well a source. Identified by a match (e.g.
cocoon://...). That is why
this.source = super.resolver.resolveURI(src);
is the same for a file: or cocoon: or ...

> >>>Is this is a reasonable guideline for locationmap usage?
> >>
> >>Yes :-)
> > 
> > 
> > I do not know, where do we draw the line? 
> > Do you mean we only allow file system resource (that means only
> > file:///...) when referring to physical resource? If so what is with
> > e.g. zip://... or any other possible protocol?
> I don't think Tim is suggesting that we restrict the range of protocols 
> in use. I think he is merely saying that we should not be creating an 
> additional level of indirection between the sitemap (which defines what 
> processing to apply) and the locationmap (which defines the location of 
> resources used in that processing).

Yeah is so he is right, but I would be against restricting the
locationmap for certain protocols.

> Ross

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)

View raw message