in reply to Re^4: Absolute simplest way to keep a database variable persistent?
in thread Absolute simplest way to keep a database variable persistent?

Instead of using a webserver, have your Perl script fork off its own server (if one isn't running at the time). It can communicate on a socket. We have a CGI program that keeps an large XSLT in standby. Using IO::Socket:
my $sock = new IO::Socket::INET ( LocalHost => $server, LocalPort => 9200, Proto => 'tcp', Listen => 2, ReuseAddr => 1, ); die "socket creation error: $!" unless $sock; while( my $client = $sock->accept() ) { binmode $client, ":utf8"; $client->autoflush(1); # Read data while( $client->recv( $in_buffer, $buffer_size ) ) { # Store data } # Process data # Return data $client->send( $output ); }
Some things to consider to make it dummy proof is allow it to adjust what port is runs on at runtime, and to have the server exit after a while to avoid zombie processes.
  • Comment on Re^5: Absolute simplest way to keep a database variable persistent?
  • Download Code

Replies are listed 'Best First'.
Re^6: Absolute simplest way to keep a database variable persistent?
by natestraight (Novice) on Oct 08, 2008 at 01:52 UTC
    Sounds possible. Thanks for the sample code, too.