Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
| No. |
Time |
User |
SHA256 |
| -r1 |
2026-10-19T06:51:34Z |
DavidTerei |
954fdbc94cda47a5060aeafa9a0e7f083727caeac9e2aa6d1b00f73e9274a153
|
|
Changed description
from A buffered Meta Text protocol client for single servers and clusters.
to A client library for a Memcached cluster. Memcached is an in-memory key-value
store typically used as a distributed and shared cache. Clients connect to a
group of Memcached servers and perform out-of-band caching for things like
SQL results, rendered pages, or third-party APIs.
It uses the Memcached Meta Text protocol and requires memcached 1.6.0 or
newer. Username/password authentication is supported through memcached's
@-Y authfile@ mode; the binary protocol and SASL authentication are no longer
supported. It supports connecting to a single, or a cluster of Memcached
servers. When connecting to a cluster, consistent hashing is used for routing
requests to the appropriate server. Timeouts, retrying failed operations, and
failover to a different server are all supported, as is Amazon ElastiCache
auto discovery.
Multi-get is supported through the pipelined @getMany@. Keys containing
whitespace or control bytes are sent using the protocol's base64 binary-key
mode.
Basic usage is:
> import qualified Database.Memcache.Client as M
>
> mc <- M.newClient [M.ServerSpec "localhost" "11211" M.NoAuth] M.def
> M.set mc "key" "value" 0 0
> v <- M.get mc "key"
You should only need to import 'Database.Memcache.Client', but other modules
are exposed for lower-level use. Version 0.4 is a breaking change from 0.3;
see the changelog for details.
|
| -r0 |
2026-10-19T06:44:33Z |
DavidTerei |
a253b0531183267fba09b90e11705f5d17dd56c08be626b3e755e2190901ef06
|
|
|