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
Scott Gifford wrote:
Colin Wetherbee <[EMAIL PROTECTED]> writes:
[...]
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 o
> I'm not sure what you're suggesting. The first few pages of "cache" on
> CPAN have some modules for caching data in memory and on disk and so
> forth, but I don't see how they relate to my problem.
>
> Which is that of notifying all of my application's perl processes when
> an update has be
Clinton Gormley wrote:
I'm not sure what you're suggesting. The first few pages of "cache" on
CPAN have some modules for caching data in memory and on disk and so
forth, but I don't see how they relate to my problem.
Which is that of notifying all of my application's perl processes when
an u
Hi. The touch file will definately work and I've used that myself but
in this case its inelegance bothers me. It's also another touch point
for administration. What I would probably do is put the state
information in the database itself. The script would keep track of the
age of its data and ev
10 matches
Mail list logo
