On Sun, Jun 29, 2003 at 11:34:01AM +0200, Nicola Ken Barozzi wrote:
> Jeff Turner wrote, On 29/06/2003 8.03:
...
> >- We're abusing the name 'transformer', since nothing is transformed.
> >  If we're really going to go this way, let's define a new sitemap
> >  element, <map:link-gatherer/>.
> 
> There are transformers that do not transform, it's not unusual,

I can't think of any others?

<snip links to stuff I mostly missed - thanks>

> "
> So basically we are adding a contract to the sitemap, by saying that
> each sitemap implementation has to provide a list of links if requested
> to (as seen above).
> "
> 
> As you state, a Transformer does not feel right. In fact, a sitemap has 
> now a new contract that it has to give links. The question is: how can 
> it be made more versatile? Who can we tell the pipeline where we want 
> the link gathering to occur?
> 
> What about a named pipeline that is inserted by the link gatherer where 
> it gets the links? What about using a spacial label to indicate where to 
> gather links?

Hmm.. interesting.  Perhaps we just need to augment Resources a bit:

<map:resource name="gather-links" from-position="content">
  <!-- Any required link munging -->
  <map:transformer type="gather-links"/>
</map:resource>

Ie, a Resource inserted in each pipeline after the 'content' label.
Rather AOP'ish.

> Just food for thought.

Tasty..

--Jeff

> -- 
> Nicola Ken Barozzi                   [EMAIL PROTECTED]
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------

Reply via email to