Suppose that I wanted to make a hash persistent so that it's contents were
shared between processes.  Does the persistence mechanism keep a single copy
and protect access to it using semaphores, or is it more like the mySQL
pconnect way where a currently idle connection is used instead?

What I have in mind is a file-contents cache in order to speed up the
performance of a templating system.  Can I use a (true) global hash table in
my extension and do everything via the persistent version of emalloc, or do I
have to consider something else?

I realize that there might not be a huge increase in performance, but it would
be nice to know how to do it so that if we needed that bit of extra speed, we
could get it.


PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to