Re^2: [mod_perl] when does it keep data in memory?

stvn++, thanks for the nice explanation.
I assume from your story that there is no (in-memory) way to make the child's changes visible to the other processes?

Comment on Re^2: [mod_perl] when does it keep data in memory?

Replies are listed 'Best First'.
Re^3: [mod_perl] when does it keep data in memory? by stvn (Monsignor) on Nov 28, 2004 at 02:33 UTC
I assume from your story that there is no (in-memory) way to make the child's changes visible to the other processes? You can try using some kind of shared memory caching, there are a number of CPAN modules for this, but I think it only works on a few OSes. When you are programming mod_perl like this you are basically programming a multi-process application, so you have all the usually Interprocess communication (IPC) issues that go along with it. To be honest, probably the best thing would be to try and fit this all into a database though (if that was possible) since that will have the best concurrency and data integrity checks. But since I don't know the format and content of your data-structure I cannot say if that makes sense. -stvn	[reply]

Replies are listed 'Best First'.

Re^3: [mod_perl] when does it keep data in memory?
by stvn (Monsignor) on Nov 28, 2004 at 02:33 UTC

I assume from your story that there is no (in-memory) way to make the child's changes visible to the other processes?

You can try using some kind of shared memory caching, there are a number of CPAN modules for this, but I think it only works on a few OSes. When you are programming mod_perl like this you are basically programming a multi-process application, so you have all the usually Interprocess communication (IPC) issues that go along with it.

To be honest, probably the best thing would be to try and fit this all into a database though (if that was possible) since that will have the best concurrency and data integrity checks. But since I don't know the format and content of your data-structure I cannot say if that makes sense.

-stvn

[reply]