view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    "pread"/"pwrite" via "IO::FD") will need to be performed to set the
    position for correct IO operation.

    Sweeping the cache should be done a regular interval to keep the meta
    data fresh, but long enough to make the cache useful. To make this
    module event system agnostic it is up to the user to implement a timer
    that calls the "sweep" API.

    A cached entry contains a "USER" field, which allows the user to store
    associated meta data with the entry. For example this could be used to
    store pre rendered HTTP headers (content-type, content-length, etag,
    modification headers, etc), which only need to be computed when the file
    was opened.

API
    An OO API is provided for configuration and ease of use and an
    additional functional API for best performance for high frequency
    access.

  Cache entry
    A cache entry is an anonymous array with the following fields:

README.md  view on Meta::CPAN

the file, appropriate calls to `seek` (or `pread`/`pwrite` via `IO::FD`)
will need to be performed to set the position for correct IO operation.

Sweeping the cache should be done a regular interval to keep the meta data
fresh, but long enough to make the cache useful.  To make this module event
system agnostic it is up to the user to implement a timer that calls the
`sweep` API.

A cached entry contains a `USER` field, which allows the user to store
associated meta data with the entry. For example this could be used to store
pre rendered HTTP headers (content-type, content-length, etag, modification
headers, etc), which only need to be computed when the file was opened.

# API

An OO API is provided for configuration and ease of use and an additional
functional API for best performance for high frequency access.

## Cache entry

A cache entry is an anonymous array with the following fields:

lib/File/Meta/Cache.pod  view on Meta::CPAN

the file, appropriate calls to C<seek> (or C<pread>/C<pwrite> via C<IO::FD>)
will need to be performed to set the position for correct IO operation.

Sweeping the cache should be done a regular interval to keep the meta data
fresh, but long enough to make the cache useful.  To make this module event
system agnostic it is up to the user to implement a timer that calls the
C<sweep> API.

A cached entry contains a C<USER> field, which allows the user to store
associated meta data with the entry. For example this could be used to store
pre rendered HTTP headers (content-type, content-length, etag, modification
headers, etc), which only need to be computed when the file was opened.
 


=head1 API

An OO API is provided for configuration and ease of use and an additional
functional API for best performance for high frequency access.