On 5/5/07, Will Fould <[EMAIL PROTECTED]> wrote:
But, I'd like to do something similar; have a separate process that can alter parent data receive signals and re-cache accordingly.
There's no way to alter data in the parent process without restarting the server.
Of course, the problem with using a database to get the lists (besides the lists being the result of a munge), is that they are rather large.
Ideally you would load only the part you need, rather than the whole thing. A local shared storage method, like BerkeleyDB or MySQL over Unix-domain sockets, can be very speedy. If you absolutely need all of it in memory in each process and it's going to change, I don't know any way to beat what you're already doing. - Perrin
