Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Readme unclear regarding namespacing #45

Open
rethab opened this issue Jan 20, 2016 · 1 comment
Open

Readme unclear regarding namespacing #45

rethab opened this issue Jan 20, 2016 · 1 comment

Comments

@rethab
Copy link

rethab commented Jan 20, 2016

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.

@hayd
Copy link
Contributor

hayd commented May 4, 2018

I also found this unclear (I was unable to find key/values set in play from another app), thanks for this issue it makes sense. I found them as s"default${key}".

however suggests that the key memcached.namespace is never read

See also #41 . Note: the name "defaultCache" is confusing... when it's really "cachePrefix".

NOTE: To configure override play.cache.defaultCache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants