Ciao!
From an Embperl page, I am creating a SELECT/OPTION widget that is
populated with the results of a database query. The content of this
database source is relatively static over time, so I would like to only
have to hit the database once, create a perl structure of the results if
it does not already exist, and store it away somewhere for subsequent
use by *all* sessions.
Is this a recommended use of the %mdat hash? Frankly, I'm hesitant to
consider a 'global' data structure such as this, but since it isn't
subject to change for the life of the Apache server children, I can't
see any problems with it hanging around for all sessions to use. I'm
just needing to craft a way to make it persist and globally available.
Suggestions welcome ...
Peace.
From an Embperl page, I am creating a SELECT/OPTION widget that is
populated with the results of a database query. The content of this
database source is relatively static over time, so I would like to only
have to hit the database once, create a perl structure of the results if
it does not already exist, and store it away somewhere for subsequent
use by *all* sessions.
Is this a recommended use of the %mdat hash? Frankly, I'm hesitant to
consider a 'global' data structure such as this, but since it isn't
subject to change for the life of the Apache server children, I can't
see any problems with it hanging around for all sessions to use. I'm
just needing to craft a way to make it persist and globally available.
Suggestions welcome ...
Peace.