On Thu, Oct 29, 2009 at 12:13 AM, Mahesh Khambadkone
wrote:
> Confused slightly by the Apache phases and how it plays with older CGI
> scripts, what would be the best way to implement this in-memory cache
> that can be dirtied from time to time?
You can't keep things in memory with CGI scripts be
On Thu 29 Oct 2009, Mahesh Khambadkone wrote:
> As it seldom changes, we dont want to use a database for these
> 'config values', yet need a way to retain in memory and dirty its'
> value from time to time.
Have a look at MMapDB which I have just uploaded to CPAN.
I wrote this module some time ag
2009/10/28 Mahesh Khambadkone :
> Confused slightly by the Apache phases and how it plays with older CGI
> scripts, what would be the best way to implement this in-memory cache
> that can be dirtied from time to time?
I would suggest using memcached. It's a daemon that will hold your
data in memo
Hi,
We run a script, server.cgi, running on a Apache2 instance using
mod_perl support for 'older' CGI scripts.
server.cgi is called by multiple individual clients at a time,
returning an XML. It contains some config values that change from
time to time (once a week) e.g, campaign end date
As it
