>>>The 'is-logged' attribute is a Boolean that is set upper in the pipeline
>>>inside an action. The action sets correctly the 'is-logged'
>>>attribute.
> so the is-logged attribute that is the critical change in your use-case
> is set inside an action. This could be the problem ...
I would love to be sure that the problem is in my code.
> because cocoon
> evaluates the pipeline cache keys and validities *before* it executes
> any pipeline components.
I directed the Action, Generator and CachingProcessingPipeline logger to
the same file to see how the components are called.
And I found the following results:
First hit:
- Action.act --> is-logged is set here
- Generator.configure
- Generator.setup
- Generator.getKey
- Generator.getValidity
- AbstractCachingProcessingPipeline
+ getValidityForInternalPipeline
+ Cached response not found
....
+ caching content for further requests...
Second hit:
- Action.act --> is-logged is set here
- Generator.setup
- Generator.getValidity
- AbstractCachingProcessingPipeline
+ Found cached response for
+ using valid cached content
--> Generator.getKey
+ getValidityForInternalPipeline
...
So, from what is see in my log it seems my action
act method is executed *before* the key and validities
of the other components are evaluated.
How can this be?
Anyway. As I said, I have solved my problem by changing
the urls used for the logged state vs. unlogged state.
Oscar
__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
