Thanks for the answers so far, this is really the kind of stuff I was
hoping for. I appreciate even the 2-cent suggestions ;-), they are not
2-cents to me.
Keep them coming.
About the MySQL suggestion : I have been thinking about the same lines,
specially since with DBI, it solves several issues at once.
My doubts in that respect have been that it would introduce one more
dependency (MySQL) in the application software in general.
The whole application package is multi-platform (Linux, various Unixes,
Win32) so any dependency can easily become a problem or an installation
hassle on one or the other platform. (That is for instance one reason
why I am not using one of the modules based on Unix-like shared memory.)
Also, doing this with an RDBMS also means defining and creating the
tables in advance to hold the data and so on, which is also an
additional initial setup burden.
So I do take note, but if anyone can think of other alternatives, please
keep posting.
I think it may be better to start a separate thread for this specific
question about "sharing" such a table over many requests.
