in reply to The Singleton design pattern and fork();

Other people told you to go learn shared memory and/or IPC. You could also re-architect and use a shared BerkeleyDB database which supports concurant access, transactions and locking. Or I'd use that because I usually have BDB already handy.

Seeking Green geeks in Minnesota

  • Comment on Re: The Singleton design pattern and fork();

Replies are listed 'Best First'.
Re: The Singleton design pattern and fork();
by skx (Parson) on Feb 22, 2003 at 17:23 UTC

     Thanks for the suggestion - looks like I'll go with DBI.

     (The original singleton I had planned was just a temporary measure until I wrote the DBI code to store this information for real).

    Steve
    ---
    steve.org.uk
[reply]

In Section Seekers of Perl Wisdom