Memcache, for example, is explicitly not meant to be run with "public access", as it is not secured against attacks. I am pretty sure the same applies to redis.<p>If my assumption is correct, i wonder why one should use a (potentially slower) http client or protocol in favor of the "native" protocol.
There's also Bone which implements SET, GET, and KEYS over HTTP(S). It also uses something similar to the Amazon S3 request signatures for authentication.<p><a href="https://github.com/solutious/bone" rel="nofollow">https://github.com/solutious/bone</a>