/usr/share/doc/cl-memstore/memstore.html is in cl-memstore 1.1.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 | <h1>Memstore</h1>
<p><em>A high-level interface for the memcached and membase servers</em></p>
<p>Written by Kevin M. Rosenberg <a href="mailto:kevin@rosenberg.net">kevin@rosenberg.net</a></p>
<h2>Downloads</h2>
<ul>
<li>The web site for memstore is <a href="http://memstore.b9.com/">http://memstore.b9.com/</a></li>
<li>A git repository is available at <a href="http://gitpub.b9.com/memstore.git">http://gitpub.b9.com/memstore.git</a></li>
<li>Releases are available for download at <a href="http://files.b9.com/memstore/">http://files.b9.com/memstore/</a></li>
</ul>
<h2>Prerequisites</h2>
<p>This library incorporates a heavily modified version of <code>cl-memcached</code>
version 0.4.1. The primary need for the modification is to support the
<code>flags</code> field supported by the memcached server. The flag field is
used to store information required to deserialize the object data from
memcached. In addition to adding the <code>flags</code> field, the library has
been heavily refactored. For more information on the changes in
memcache, see <a href="memcache.html">memcache</a>.</p>
<p>This library also requires Common Lisp libraries of
<a href="http://gitpub.b9.com/kmrcl.git">kmrcl</a>,
<a href="http://common-lisp.net/project/cl-store/">cl-store</a>,
<a href="http://weitz.de/flexi-streams/">flexi-streams</a>,
and <a href="http://common-lisp.net/project/zlib/">zlib</a>.</p>
<h2>Overview</h2>
<p>Memstore allows efficient storing of simple objects as well as
easy storing of complex objects and optional compression.</p>
<p>When storing an object, if the object is a string then that is
directly written to the memcached server. For non-strings, an attempt
to made to write the object to a string with <code>*print-readably*</code> bound
to <code>t</code>. If that succeeds, then the string is converted to a vector of
octets. If that fails, the <code>cl-store</code> is used to serialize that object
to a vector of octets.</p>
<p>Next, optional compression is applied to the octets. First, the
<code>*compression-enabled*</code> flag is checked to see if compression is
enabled. Next, the length of the objects is compared to
<code>*compression-threshold*</code>. Only objects larger than
<code>*compression-threshold*</code> will be compressed. For objects that qualify
for compression, the size of the compressed object is compared to the
length of the uncompressed object to decide if the object is shrunk
enough to make the compression worthwhile.</p>
<p>The <code>flags</code> parameter to cl-memcached stores whether cl-store or
write-to-string is used to serialize the object and whether
compression is applied. <code>mem-restore</code> uses those flags to determine
how to reconstruct the object.</p>
|