> I guess to only way to solve my problem is to write my own extension to
> initialize my objects in my own memory (even can keep them in local memory, as
> long as they are persistent across requests). You mentioned to write a MINIT
> hook; could you give some more details? Is there any document
...
H... well, file_get_contents() doesn't lock the file so I'm
interested in how you're accomplishing this feat. Perhaps you're
creating a temporary directory (atomic IIRC) for the filename and then
flocking that? I dunno, I hate race conditions.
I was to fast with that, I didn't look in
Jason Barnett wrote:
* Is file_get_contents the fastest way to open the file?
AFAIK yes it is since it takes advantage of memory mapping (where
possible).
* Is serialize the fastest way to serialize ;) ?
Not sure.
* Are there any other things I should consider? (I'm aware of
file-locking issu
> I think I need to prevent the pages from beeing cached. How this can > be
done? I'm totally inexperinced with this stuff.
Look at the examples and user notes in the header statement in the manual.
http://php.net/function.header
That should help you, they have a whole section on how to stop ca
One rather brute force way to get round this is to append a unique (per-session
at least) id to the querystring of each page, which means that the page will be
requested from the server rather than the cache. I believe this works in Opera
as well as other browsers.
There is more to cache-contro
Many thanks for all the answers.
I've checked that I was saving the right file (I even think about it
!), and even if I'm using Templeet (sort of smarty http://templeet.org
) i've disabled all cache, and this code is only PHP not
template-language.
I've checked the error.log, and it just said that
6 matches
Mail list logo