Re: Where to save module data

This may be a gap in the market:

permanently-available files are best handled with File::ShareDir::Install and are read-only
ephemeral ones with File::Temp owned by app-process owner; need not survive a reboot

Your situation is probably closer to ephemeral, both in terms of lifespan, and appropriate file-ownership. But my assumption is you'd want to have the files survive a reboot? This situation is like a file-based, age-limited memoisation. You might consider using Redis also.

Comment on Re: Where to save module data

Replies are listed 'Best First'.
Re^2: Where to save module data by Bod (Parson) on Oct 08, 2024 at 21:01 UTC
But my assumption is you'd want to have the files survive a reboot? For my current purpose...no! It is on a webserver which pretty much never gets rebooted. But, of course, for the hypothetical CPAN module, surviving a reboot would be preferable so it could be used anywhere Perl can exist.	[reply]