Open rdegges opened 10 years ago
We do pass along the options directly, see:
https://github.com/stormpath/stormpath-sdk-node/blob/master/lib/cache/MemcachedStore.js#L20
The way you're trying to pass the connection, as an object with named keys, is not supported by the node-memcached module. See the object documentation here
All that said, I did find two things that should be changed:
I'm removing the bug label
@robertjd please create issues to fix the default port to 11211
so we don't lose this.
Actually, nm, we can use this issue to reflect that work. Sorry for the noise!
:) yep that was the idea
In 0.6.0 the port documentation has been fixed and the connection value is now documented as "sever location"
Note: in code, the "sever location" value is still using a property called "connection"
I want to change that property to be called "severLocation", which will be a breaking change.
Adding 1.0 Label
In the API docs for memcached -- it shows in the sample that the connection string is specified as
127.0.0.1:11211
. When I tried this, it works.In the docs, however, it says that the
connection
variable can be a string or an object. When I try the following, I get errors:I believe what we should do is ensure that all backends support an object for the connection variable, and ensure they all support the standard host / port options -- this way it makes integration a lot simpler.