Re: Cache checking on the Node Process step (STEP 2)

Igor Vylusko wrote:
(about caching)
> What reason it not be done earlier?
> May be there are some issues on it?

Because it depends on what are your "seeds", that are the values on 
which your output depends. If you need to read something in db depending 
on a param received by GET, you cannot test for caching being you read 
your values.

> Also, a have find out that no persistent db connection used all over
> in binarycloud(Auth, Perm, ...), although there is persistent property in dataset
> config of skeleton package.

Persistent connection in php is not always recommended. In some cases, a 
persistent connection leads to bugs. Maybe it's a param to add to 
Datasources.conf: persistent boolean default true.

>>>Where can I get performance tips and issues for the framework and my app
>>>based on it tuning?
> 
> JCM> I'm afraid it's a chapter we have to write togehter ;-)
> JCM> Please suggest some ehancements, and maybe open a draft on the wiki.
> 
> Let's try, my English is poor, but I'll try do the best I can.

Start a draft on the wiki, then post here and we'll discuss it.

>>>May I alter server response cache control options for the particular
>>>page(Node)?
> 
> 
> JCM> Of course, change your cache settings in the Node in _setDefaults();
> 
> I meant server response cache control setings, if you as well, could
> you please explain it in detail.

Do you want to change the behaviour of the cache for already cached 
pages? What real case do you have in mind?


-- 
Jean-Christophe Michel