| 1 |
Source: libcache-memcached-managed-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: Nick Morrott <[email protected]> |
| 4 |
Section: perl |
| 5 |
Testsuite: autopkgtest-pkg-perl |
| 6 |
Priority: optional |
| 7 |
Build-Depends: debhelper-compat (= 13) |
| 8 |
Build-Depends-Indep: libcache-memcached-perl <!nocheck>, |
| 9 |
libsocket6-perl <!nocheck>, |
| 10 |
memcached <!nocheck>, |
| 11 |
netbase <!nocheck>, |
| 12 |
perl |
| 13 |
Standards-Version: 4.7.2 |
| 14 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libcache-memcached-managed-perl |
| 15 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libcache-memcached-managed-perl.git |
| 16 |
Homepage: https://metacpan.org/release/Cache-Memcached-Managed |
| 17 |
Rules-Requires-Root: no |
| 18 |
|
| 19 |
Package: libcache-memcached-managed-perl |
| 20 |
Architecture: all |
| 21 |
Depends: ${misc:Depends}, |
| 22 |
${perl:Depends}, |
| 23 |
libcache-memcached-perl, |
| 24 |
memcached |
| 25 |
Recommends: libsocket6-perl |
| 26 |
Description: API for managing cached information |
| 27 |
The Cache::Memcached::Managed module provides an API to values, cached in |
| 28 |
one or more memcached servers. Apart from being very similar to the API |
| 29 |
of Cache::Memcached, the Cached::Memcached::Managed API allows for |
| 30 |
management of groups of values, for simplified key generation and expiration, |
| 31 |
as well as version and namespace management and a few other goodies. |
| 32 |
. |
| 33 |
Over the functionality provided by the Cache::Memcached module, this module |
| 34 |
provides: automatic key generation, ID refinement, version management, |
| 35 |
namespace support, group management, easy (default) expiration specification, |
| 36 |
automatic fork() detection, magical increment, instant invalidation, |
| 37 |
dead memcached server detection, starting/stopping memcached servers and an |
| 38 |
extensive test-suite. |
| 39 |
. |
| 40 |
The basic premise is that each piece of information that is to be cached, |
| 41 |
can be identified by a key, an optional ID, a version and a namespace. |
| 42 |
The key determines the basic identification of the value to be cached. |
| 43 |
The ID specifies a refinement on the basic identification. The version |
| 44 |
ensures that differently formatted values with the same key and ID do not |
| 45 |
interfere with each other. The namespace ensures that different realms |
| 46 |
of information (for instance, for different users) do not interfere with each |
| 47 |
other. |