+
+ +
+

Bugs, Known Issues and Insufficiencies¶

+
+

libhashkit¶

+

libhashkit is not usable for general purpose hashing, because it is geared to +usage by libmemcached.

+
+

MurMur¶

+

Hashkit's MurMur/MurMur3 are limited to the lower 32 bits.

+
+
+

crc32¶

+

Commit "More Hashing methods" +from October 2007 first released in v0.8, which main intention seems to have +been to add FNV1 hash algos, changed the result of the crc32 hash to only its +upper 16 bits sans MSB, without any additional comment.

+

The implementations referred to in the file header (Postgres and BSD) +do not exhibit this behavior.

+

A bug report was +filed three years later on launchpad, which was marked Won't fix with +the comment that it was for compatibility with other "drivers", which +supposedly refers to other memcached client libraries.

+
+
+
+

libmemcached¶

+
+

Replication¶

+

This is a somewhat badly named feature, because it does not provide +any of the guaranties one would expect from a proper replication.

+

One can set the intended number of additional servers where data should +be stored with the behavior MEMCACHED_BEHAVIOR_NUMBER_OF_REPLICAS and +specify whether MGETs/GETs should read from a random server with +MEMCACHED_BEHAVIOR_RANDOMIZE_REPLICA_READ. DELETEs will try to +delete the key from all replicas.

+

The binary protocol is required and any other command is unaffected.

+
+
+

TLS/SSL¶

+

libmemcached does not support TLS/SSL, yet. +See github issue #37.

+
+
+

Coroutines and event loops¶

+

libmemcached does not support explicit asynchronous usage, yet. +See github issue #54.

+
+
+

META protocol¶

+

libmemcached deos not support memcached's META protocol, yet. +See github issue #121.

+
+
+
+ + +
+ +