Dear All
I've writen a small IPC sysV based shared cache thingy ... (useing
IPC::ShareLite), and I'd like some comments oin the design if anywants
to crtique...
Why / the problem:
I work in a dept where the coderes (Me !) code, and the HTML design
people do HTML. The only commonality we share
[EMAIL PROTECTED] wrote:
Sorry, sounds like you could have just used Apache::StatINC, no?
Apache::StatINC only reloads your perl modules if they change.
My module loads (HTML) templates into a shared IPC memory segment - or
rather anything that can be stored as a scalar (limits of
[EMAIL PROTECTED] writes:
[No StatINC because...]
I do not use it to store perl modules, only to store all my html templates.
Does that make sense ?
Well, it isn't scalable past one machine, you know. As long as you are willing
to live with that, fine.
If that is a problem, I'm not sure if
MAIL PROTECTED]
Sent: Friday, July 21, 2000 8:58 PM
Subject: YAM (Yet Another Module) - an IPC shared cache thing - anyone
interested ?
Dear All
I've writen a small IPC sysV based shared cache thingy ... (useing
IPC::ShareLite), and I'd like some comments oin the design if anywants
to crtique...
Francesco Pasqualini wrote:
is it possible to use IPC sysV to share DBI connection between apache
childs ?
IIRC this is not possible as DBI connections are special magic things -
this was discussed on the list a few months back - but I cannot remember
the name of the thread.
Greg Cope
Greg Cope wrote:
Dear All
I've writen a small IPC sysV based shared cache thingy ... (useing
IPC::ShareLite), and I'd like some comments oin the design if anywants
to crtique...
Why / the problem:
I work in a dept where the coderes (Me !) code, and the HTML design
people do HTML.