I shall have a look at Config::Any as a solution
If you are using some kind of web environment (e.g. CGI), be VERY careful with write access to the configuration. You need to ensure that no process reads the config file while it is rewritten, or else some settings may get lost. You also need to ensure that at most one process writes the config file at any time. Both can be handled with file locking and atomic renames, but it is easy to implement wrong. It is WAY easier and safer to put the configuration in the database that you already use.
Alexander
In reply to Re^3: Storable for user preferences
by afoken
in thread Storable for user preferences
by Bod
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |