Greetings.
I have an application that accesses some relatively static database
tables to create drop-down lists. As an example, one of these
tables is a list of common commercial aircraft.
At the moment (and not in a production environment), every time the
drop-down list is generated for a
Colin Wetherbee wrote:
At the moment (and not in a production environment), every time the
drop-down list is generated for a web page, the script queries the
database to retrieve the entire list of aircraft. I would prefer to
retrieve the list of aircraft when each Perl interpreter starts and
John ORourke wrote:
Colin Wetherbee wrote:
At the moment (and not in a production environment), every time the
drop-down list is generated for a web page, the script queries the
database to retrieve the entire list of aircraft. I would prefer to
retrieve the list of aircraft when each Perl in
Colin Wetherbee wrote:
John ORourke wrote:
Colin Wetherbee wrote:
Wouldn't a simpler approach be to just restart Apache when you want
to update the lists? You could even have the 'add to list' function
send SIGUSR1 to the parent Apache, causing a graceful restart.
I'm trying to avoid restar
John ORourke wrote:
Colin Wetherbee wrote:
John ORourke wrote:
Colin Wetherbee wrote:
Wouldn't a simpler approach be to just restart Apache when you want
to update the lists? You could even have the 'add to list' function
send SIGUSR1 to the parent Apache, causing a graceful restart.
I'm t
On Jan 13, 2008 4:19 PM, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
> I thought about the file thing... if the file exists, check its last
> modified timestamp; if that timestamp is greater than the stored
> timestamp, then update the data from the database. It seems like
> unnecessary disk access
