Re: Pool Module Question

"Jonathan Ellis" <[email protected]>
Newsgroups gmane.comp.python.spyce.general
Message-ID <[email protected]>
On Fri, 14 Apr 2006 14:25:07 -0600, "Ben Ringold"
<ben-3GbDDtM/[email protected]> said:

> I implemented an expiring data cache using Spyce's pool module to store
> the cached objects.  It appears that there are multiple instances of the
> pool dictionary on a single server, rather than the single pool I
> anticipated.  This is fine for objects that can persist through the life
> of the server instance (database connections etc) but many of the objects
> I'd like to cache would only be relevent for a few minutes, so multiple
> pools don't seem to offer much processing relief. 
> 
> Does every client thread have it's own pool?  Is there anyway to
> implement a more unified data cache? 

If you're using an old version of Spyce, each _process_ does have its
own pool.  2.x versions should detect this and store pool objects as
pickle files to preserve the "only one pool" property.  What version of
Spyce are you using, and how are you connecting it to Apache?

-Jonathan
-- 
C++ is history repeated as tragedy. Java is history repeated as farce.  --Scott McKay



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.