cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: More problems with implementing servlet services
Date Fri, 18 May 2007 12:37:09 GMT
Grzegorz Kossakowski wrote:
> Vadim Gritsenko pisze:
>> Grzegorz Kossakowski wrote:
>>> Vadim Gritsenko napisaƂ(a):
>>> For pipelines consisting of only generators, transformers and 
>>> serializers it's really easy to implement (I have a patch for it 
>>> already done). However, how do you see it could be implemented 
>>> *automatically* for actions and flowscripts?
>> IIRC, tree processor can happily build a pipeline even if there are 
>> actions in the sitemap - so that is not a problem.
> I don't get these. Action has only one method act() where e.g. database 
> operations and status code can be mixed. If we call act() during 
> processing of HEAD request we will have side effects (db operations) 
> otherwise we will not have a proper value of status code that we are 
> supposed to return in response to the HEAD request.
Just to complete the picture, the same problems arise with caching (at 
least with the default pipeline based caching): even if the response is 
answered from the cocoon cache, actions and flow script are triggered.


View raw message