Thanks for your thoughts.
My first thought would be to use a shared memory segment. See
http://us4.php.net/shmop. Memory leaks are an issue, but not a
show-stopper. One has to program well and be careful to get a
Charles Corrigan wrote:
>My understanding is that, to avoid potential memory (and other resource) leaks taking down the webserver, there has been a conscious
>design decision to implement php as not keeping any memory context between http requests. I understand that there are ways around
>this but they are not straightforward.
>>From: Dan Frankowski [mailto:dfrankow@...]
>>Sent: 03 May 2005 22:08
>>Subject: [Phpwiki-talk] PHP persistent caching
>>I have a question for experienced PHP developers. There is a lot of
>>information I can imagine wanting to cache across sessions in PHP. For
>>example in WikiLens, a ratings database, or per-item statistics (#
>>ratings, averages, etc). This is stuff that will fit in-memory for the
>>What's the best way to do that in PHP? I've looked at a couple of PEAR
>>modules (e.g., "Cache" included in PhpWiki), and they seem to be
>>file-based. This is astonishing to me. Clearly memory can be 1000 times
>>faster than disk (although there are usually memory-based disk caches,
>>too). Is it really best to use file-based caches? I thought about
>>writing a shared memory-based cache, and a colleague warned me away from
>>it, saying shared memory access in PHP is iffy.
>This SF.Net email is sponsored by: NEC IT Guy Games.
>Get your fingers limbered up and give it your best shot. 4 great events, 4
>opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
>win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
>Phpwiki-talk mailing list