cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: [RT] Virtual Sitemap Components
Date Wed, 21 Jul 2004 16:49:29 GMT
Vadim Gritsenko wrote:

> Sylvain Wallez wrote:
>> Reinhard Poetz wrote:
>> <snip/>
>>> I have the same understanding after reading the whole thread. Though 
>>> I'm not sure if we have consensus on actions. Anyway, what will be 
>>> the order of execution of actions? IIUC all actions within a pipeline 
>>> are execute *before* the pipeline is executed, aren't they? Will this 
>>> behaviour remain?
>>> Another question: Is this order of execution of actions by design and 
>>> if yes, what's the reason?
>> Hey Reinhard, back to basics! Actions are in the "control structure" 
>> category, alongside match and select. So they must be executed first, 
>> just as matchers and selectors, as their result is used to decide 
>> which components are included in the pipeline.
>> The problems of actions is that they are more than control structures 
>> as they are allowed to modify the system state, or perform a redirect, 
>> which is not what the pipeline instructions (<map:generate> 
>> <map:transform> etc) are doing today. That's why actions may be 
>> forbidden in VPCs, except maybe for virtual readers.
> Any Action can be re-written as a Matcher in 10-15 seconds (only 
> exception is this redirect mentioned above... shall we remove redirector 
> from action interface? ;-) ). Thus, I totally miss the point why actions 
> should be disallowed.

because actions redirect and we don't allow things to happen behind your 
back (think in the case you use a VPC without having written it 
yourself, as for real block scenarios).


View raw message