Taking a look at mod_mem_cache source code i have seen that it doesn't
use pools to allocate cache objects but i does so by means of
reference counting and simple calloc/free calls. I have also seen
that this module requires a Threaded apr to work. I am wondering the
reasons of this design choices
luca regini wrote:
Taking a look at mod_mem_cache source code i have seen that it doesn't
use pools to allocate cache objects but i does so by means of
reference counting and simple calloc/free calls. I have also seen
that this module requires a Threaded apr to work. I am wondering the
reasons of
On Tue, 8 Mar 2005, Bill Stoddard wrote:
> luca regini wrote:
> > Taking a look at mod_mem_cache source code i have seen that it doesn't
> > use pools to allocate cache objects but i does so by means of
> > reference counting and simple calloc/free calls. I have also seen
> > that this module req
luca regini wrote:
Taking a look at mod_mem_cache source code i have seen that it doesn't
use pools to allocate cache objects but i does so by means of
reference counting and simple calloc/free calls. I have also seen
that this module requires a Threaded apr to work.
If you use prefork, each child
I am going to use shared memory. I found a very good example in the
ssl_scache_shmht.c file. This implementation has everything i need of.
Now i am just working to remove dependencies that this code has on
other mod_ssl files, so to provide a generic
shared memory cache table object. I can release