[Xitami] Serving an (un)changed file.

[Ervin Kosch]

Just a couple of thought but how about these meta tag:
/<META HTTP-EQUIV="expires" CONTENT="Wed, 26 Feb 1997 08:21:57 GMT">/  - 
Have the PHP write the current date and time into the tag.
/<META HTTP-EQUIV="Pragma" CONTENT="no-cache">/ - Also forces the 
browser to not cache the content of the page

I know there are PHP Header() function equivilats to these meta tags as 
well.

Trent Reimer wrote:

>hi Hace,
>
>thanks for getting back to me and sorry if I was unclear. The problem I was
>having is that indeed I only got a new processed version when the file
>itself changed. The reason this was not helping me is that the file was
>pulling information from a database and the database was changing. Just
>because the PHP file itself did not change didn't mean that it shouldn't be
>re-processed. Whenever I changed the file itself (I just added a space
>character at the end of a line) sure enough the PHP file was re-processed
>and I got the latest info from the database.
>
>Looking at some of the other helpful comments I may take a look at the PHP
>settings.
>
>My thanks to you Thomas and Regis for looking into this.
>
>Trent
>
>
>----- Original Message -----
>From: "Melle Koning" <hace_x@yahoo.com>
>To: <xitami@lists.xitami.org>
>Sent: Thursday, May 30, 2002 7:36 AM
>Subject: [Xitami] Serving an (un)changed file.
>
>
>  
>
>>>With Xitami I'm only getting a true
>>>recheck if the PHP file itself
>>>has changed. This is a concern as an unchanged PHP
>>>file could normally be used to bring up
>>>information which changes regularly in a database
>>>for example.
>>>Any ideas?
>>>      
>>>
>>Now in your last sentence, what is it: Has the PHP
>>file changed or not? If it has not changed, Xitami is
>>doing a good job of providing a cached copy. If the
>>PHP file HAS changed, than Xitami is of course doing a
>>good job of processing the PHP file again (pulling, as
>>you say) and serving the new file up.
>>
>>Be clear: What's your concern?
>>
>>Greetings,
>>Hace
>>    
>>