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

Hello Jean-Christophe,

Sunday, February 20, 2005, 8:27:23 PM, you wrote:
JCM> (about caching)
>> What reason it not be done earlier?
>> May be there are some issues on it?
JCM> Because it depends on what are your "seeds", that are the values on
JCM> which your output depends. If you need to read something in db depending
JCM> on a param received by GET, you cannot test for caching being you read
JCM> your values.

This "seeds" check may be performed on process step(before DB and other
operations). Isn't it?
May be there where some more deep reasons and/or issues to don't do it?

>> 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.
JCM> Persistent connection in php is not always recommended. In some cases, a
JCM> persistent connection leads to bugs. Maybe it's a param to add to
JCM> Datasources.conf: persistent boolean default true.

This param is already included/implied to Datasources.conf but not used at all in
binarycloud code. Creole getConnection function is called only with one
parameter (dns) and second parameter(flags) is omitted, thus existing
binarycloud code doesn't not support persistent connections.

>>>>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.
JCM> Start a draft on the wiki, then post here and we'll discuss it.

Sorry for my ignorance about wiki, where I should get account to use
wiki in edit mode? My tigris account was denied by the wiki.
Where (what site section) shoud I create the draft?

>>>>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.
JCM> Do you want to change the behaviour of the cache for already cached
JCM> pages? What real case do you have in mind?

I talk about project properties
    <property name="Cache-Control">no-store, no-cache, must-revalidate, pre-check=0, post-check=0, max-age=0</property>
    <property name="Pragma">no-cache</property>
Can I change this for particular page/node? What is the native way and
request processing step to do it?

I think, the first performance tip is to don't make appliction do
unnecessary job i.e. to cache(with appropriate settings) all that
_may_(permited/allowed) be cached on the all app/client levels.

The second one is inference of preceding - DB connect/disconnect on
every request is unnecessary app/dbs job i.e. DB connections should be
cached too.

Correct me please if I miss.

BTW.
What engine Binaricloud site is powered by?

-- 
Best regards,
Igor.