-
-
Notifications
You must be signed in to change notification settings - Fork 456
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
Allow passing MemcachedClient for MemcachedHandle #118
Comments
Sure, that makes sense, |
@themakshter Turned out I actually need the feature myself faster as expected to test the memcached handle, so, this will be in the next release ;) |
that's awesome! thank you very much! |
Added the same option to redis, too. Now you can pass in an existing connection multiplexer. |
Hey, just to check, does this mean you cannot now just pass in the enyim section like I have been testing it, and when you just try to pass the section name to the |
…ng version suffix to satisfy beta references (hopefully)
@themakshter there is currently a bug in 0.9.3 unfortunately which causes that exception. The expected behavior is of course that it should also work with passing in the section name! I reverted some changes back and it should work normal again in the next version. |
No problem at all, it's good to know it got fixed! |
At the moment, the only way to pass in memcached settings for enyim is through adding these via the config settings. However, there may be circumstances where we might need to define our own
MemcachedClient
instance or something of the sort and set that in the CacheManager initiation. It would be nice to be able to pass in any object that implementsIMemcachedClientConfiguration
.Adding Enyim's wiki page for reference
The text was updated successfully, but these errors were encountered: