On 09.Jan.2003 -- 09:28 AM, Carsten Ziegeler wrote:
> Now, let's come to the missing part, chaining!
>
> I think we have currently two approaches:
> a) Chaining is done by special objects, so you have something like
> this (let's not discuss the "first"/"second" syntax):
>
> <map:objects>
> <map:object name="request-param" ..../>
> <map:object name="session-attr" ..../>
> <map:object name="my_chain ....>
> <first>request-param</first>
> <second>session-attr</second>
> ...
> </map:object>
> </map:objects>
> And I can simply use {request-param:myname} and {my_chain:skin}
This is how it works today. Only that it is in cocoon.xconf.
> b) Chainers (?) are special components:
>
> <map:objects>
> <map:object name="request-param" ..../>
> <map:object name="session-attr" ..../>
> </map:objects>
> <map:object-chainers>
> <map:object-chainer name="my_chain ....>
> <first>request-param</first>
> <second>session-attr</second>
> ...
> </map:object>
> </map:object-chainers>
>
> And I can simply use {request-param:myname} and {my_chain:skin}
>
> Personally I would opt for a) because b) adds another component type
> to the sitemap that is not really needed and it might be confusing
> that {request-param:myname} is handled by an object component and
> {my_chain:skin} by an object-chainer.
Right. AFAIK b) has never been proposed.
BTW the real differences have been for the case where this 'pipeline'
in a) spans several stages.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
