X-Git-Url: https://git.m6w6.name/?a=blobdiff_plain;f=BUGS.md;h=cb6f687407827b935fdf93dac8f07d23205e2abc;hb=refs%2Fheads%2Fv1.x;hp=e285ac1958b73605a91983365493799604cd5343;hpb=2022f0a313c4cbe914ea1976c539cd0c436a88a8;p=awesomized%2Flibmemcached

diff --git a/BUGS.md b/BUGS.md
index e285ac19..cb6f6874 100644
--- a/BUGS.md
+++ b/BUGS.md
@@ -2,16 +2,19 @@
 
 ## 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](./commits/1207354f)" 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.
+Commit "[More Hashing methods](https://github.com/awesomized/libmemcached/commits/1207354f)"
+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.
@@ -36,3 +39,20 @@ specify whether `MGET`s/`GET`s should read from a random server with
 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](https://github.com/awesomized/libmemcached/issues/37).
+
+
+### Coroutines and event loops 
+
+libmemcached does not support explicit asynchronous usage, yet.
+See [github issue #54](https://github.com/awesomized/libmemcached/issues/54).
+
+
+### META protocol
+
+libmemcached deos not support memcached's META protocol, yet.
+See [github issue #121](https://github.com/awesomized/libmemcached/issues/121).