Thanks for the pointers, unfortunately I've got a problem with the Shared
cache in that I need IPC::ShareLite, no problem, except it won't test ok,
I get:
PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
-I/usr/lib/perl5/i386-linux -I/usr/lib/perl5 test.pl
1..8
ok 1
ok 2
Hi all,
I eventually found the problem with getting shm to work. I had the
Openwall Linux kernel patch enabled with the "Destroy shared memory
segments not in use" option set, which most Perl IPC functions seem to not
like. Apache and PostgreSQL seem to work fine with this patch in place,
I want to cache some values in my handlers so they don't keep having to
look stuff up, and so I figured a Cache::SharedMemoryCache would be the
way to go.
I'm a little confused as to where to set the little fella up tho'. Is it
as simple as saying:
my $cache = new Cache::SharedMemoryCache(
On Tue, Mar 27, 2001 at 09:50:33PM +0100, Matt wrote:
I want to cache some values in my handlers so they don't keep having
to look stuff up, and so I figured a Cache::SharedMemoryCache would
be the way to go.
It all depends on what you want to cache and why. If you wanted to
save a trip to
DeWitt Clinton wrote:
The other question is whether or not to share the cache instance
itself globally. Technically, this is up to you. Personally I
wouldn't bother, considering the overhead of instantiating the cache
is so low that I would rather keep it local to the handler (as I did
On Tue, Mar 27, 2001 at 05:19:15PM -0500, Pierre Phaneuf wrote:
DeWitt Clinton wrote:
The other question is whether or not to share the cache instance
itself globally. Technically, this is up to you. Personally I
wouldn't bother, considering the overhead of instantiating the
cache
On Tue, 27 Mar 2001, DeWitt Clinton wrote:
Which reminds me of something. These cache objects are not currently
thread safe. When should I start expecting multi-threaded
apache/mod_perl to become mainstream enough to warrant an overhaul of
the code? I imagine that nearly most Perl
