> From: Sylvain Wallez [mailto:[EMAIL PROTECTED]]
...
> Proposed syntax for pipeline hints :
> // A hints attribute has one or more comma separated hints
> hints-attr :: hint [ ',' hint ]*
> // A hint is a name and an optional value
> // If there is no value, it is considered as a boolean "true"
> hint :: litteral [ '=' litteral ]
> litteral :: <a character string where ',' and '=' must be escaped with
'\'>
>
> This allows the following :
> pipeline-hint="caching-point, connector=profiling"
>
> Note also that sitemap variable expansion applies as usual :
> pipeline-hint="caching-point={want-cache}" where "want-cache" is a
> sitemap variable (either a Boolean or a true/false string).
>
> Talking about implementation now, what about translating this hint
> attribute to a Parameters object ? This would allow the parsing of
hints
> to be centralized in both time and space :
> - in time, because it would occur only once at sitemap load-time,
> - in space, because it will be the responsibility of the sitemap
engine,
> thus avoiding each pipeline implementation to code its own parsing.
>
> This requires a change in the Pipeline interface, since we must add
this
> Parameters object to each component addition method.
You want change interface to something like:
public interface ProcessingPipeline {
...
void setGenerator (String role, String source,
Parameters param, Parameters hint);
...
}
?
Vadim
> Thoughts ?
>
> Sylvain
>
> --
> Sylvain Wallez
> Anyware Technologies Apache Cocoon
> http://www.anyware-tech.com mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
