Projects / Perl Cache

Perl Cache

The Cache modules are designed to assist a developer in persisting data for a specified period of time. Often, these modules are used in web applications to store data locally to save repeated and redundant expensive calls to remote machines or databases. People have also been known to use Cache::Cache for its straightforward interface in sharing data between runs of an application or invocations of a CGI-style script, or simply as an easy to use abstraction of the filesystem or shared memory.


Recent releases

  •  20 Apr 2003 18:59

    Release Notes: Digest::SHA1 2.02 is now required, and IPC::ShareLite 0.09 is optionally used. Storable's "nfreeze" is now used instead of "freeze". Notes on locking and Storable were added to the README. The documentation on expiration units was updated. The quoting of the untainted path regex was modified. The duplicated get_keys in NullCache was fixed. A patch was applied to ensure consistent state if the filesystem fills up. A patch to ensure initialization of the memory cache hash was applied.

    •  11 Dec 2001 17:22

      Release Notes: This release contains newly refactored code, updated documentation, numerous clarifications, and minor bugfixes.

      •  19 Sep 2001 16:35

        Release Notes: New size aware cache implementations, replacing the Data::Dumper dependency with Storable and the IPC::Shareable dependency with IPC::ShareLite, improved and new functionality to all caches, both major and minor bug fixes and performance enhancements, and a change of the license to be either the GPL or the Artistic License.

        •  16 Feb 2001 08:26

          Release Notes: This release implements Cache::SizeAwareFileCache which extends Cache::FileCache and adds dynamic cache sizing functionalilty.

          •  14 Feb 2001 19:48

            No changes have been submitted for this release.

            Recent comments

            27 Mar 2003 12:37 shailenbellare

            can machine-independent be generated using File::Cache ?
            I have an application that is being ported to Linux from Solaris. I was wondering if there was a flag to generate m/c independent byte code so that if the application is run in Linux or Solaris, and the cache can be accessed correctly. Any suggestions would be welcome.



            Project Spotlight


            A Fluent OpenStack client API for Java.


            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.