Re^3: Storable for user preferences

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

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Comment on Re^3: Storable for user preferences

Replies are listed 'Best First'.
Re^4: Storable for user preferences by Bod (Parson) on Oct 12, 2023 at 23:17 UTC
It is WAY* easier and safer to put the configuration in the database that you already use.* Yup! I've gone for a DB solution and it is working well... I guess Storable was a case of Shiny Module Sydrome!	[reply]
Re^5: Storable for user preferences by stevieb (Canon) on Oct 13, 2023 at 06:28 UTC
I guess Storable was a case of Shiny Module Sydrome! It has its uses. You just have to understand the problem arena. You did well by asking for advice. This wasn't a good use case for `Storable` and I'm glad you listened to seasoned feedback.	[reply] [d/l]