Just a note that fflush takes care of the cache already, at least on my server. Using clearstatcache before reading a previously written file also worked, but lagged the output time much more noticeably (by two or three seconds), probably due to excess cache erasing beyond files.
fflush
(PHP 4 >= 4.0.1, PHP 5)
fflush — Invia l'output in un file
Descrizione
bool fflush
( resource $handle
)
Questa funzione forza la scrittura di tutto l'output bufferizzato sulla risorsa puntata dal puntatore handle . Restituisce TRUE in caso di successo, FALSE in caso di fallimento.
Il puntatore al file deve essere valido e deve puntare ad un file correttamente aperto da fopen(), popen() o fsockopen().
Il puntatore al file deve essere valido, e deve puntare ad un file aperto con successo da fopen() o fsockopen() (e non ancora chiuso da fclose()).
fflush
oryan at zareste dot com
31-Oct-2005 01:48
31-Oct-2005 01:48
jzho327 at cse dot unsw dot edu dot au
27-Jan-2003 09:27
27-Jan-2003 09:27
Sorry, the note I previously added regarding fflush() has a bug!
when you read file by calling
$fp = fopen("myfile", "a+");
and you wish to read the content, you have to call
rewind($fp) before you attemp to read it. (Silly me) Or else if you tried something like
$fp = fopen("myfile", "a+");
$content = fread($fp);
// show that content is in fact null
if ($content == NULL)
print "but it must be first put to rewind<br>\n";
will result
but it must be first put to rewind.
[new line]
in fact, if you are not careful (like me), and you opened it with
$fp = fopen("myfile", "r+");
$content = fread($fp);
..
// do something with content
..
then you tried to again
$content = fread($fp);
without rewind, you'd get NULL again. This sounds trivial, but if you work with several file resources, with freads and fopens everywhere, you can get easily lost. So becareful.
