The readme shows the following configuration (among others):
play.modules.cache.defaultCache=default
and then goes on to say that the namespace is empty by default and may be set with the following key
memcached.namespace=mikoto.
Looking at the code (and running an application based on this lib) however suggests that the key memcached.namespace is never read and namespace will be taken from the key play.modules.cache.defaultCache which essentially means if people are following this readme, they'll end up with a namespace called default.
I came across this issue since securesocial uses quite large keys and already provides the idLengthInBytes to restrict them, however this namespace lead to another KeyTooLongException during the migration to play 2.4.
The readme shows the following configuration (among others):
and then goes on to say that the namespace is empty by default and may be set with the following key
Looking at the code (and running an application based on this lib) however suggests that the key
memcached.namespaceis never read and namespace will be taken from the keyplay.modules.cache.defaultCachewhich essentially means if people are following this readme, they'll end up with a namespace called default.I came across this issue since securesocial uses quite large keys and already provides the
idLengthInBytesto restrict them, however this namespace lead to another KeyTooLongException during the migration to play 2.4.