-
-
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
New version / Nuget packages #372
Comments
We too are experiencing the concurrency issues and would very much appreciate a new version. |
@matthias-jauernig are you still using this library on prod? We are considering forking the repo to build dlls from dev branch, just wondering if it's stable? |
We are using "the library" in prod, but only the main branch. We got around the concurrency issue by wrapping the calls by ourselves. |
I see, thanks. Did you create locks per item key or wrapped the call site with a single lock object? |
In our case, we are locking by cache item type and cache region (if exists). public static void AddLocked<T>(this ICacheManager<T> cacheManager, CacheItem<T> cacheItem)
{
string lockKeyForAdd = typeof(T).FullName + (!string.IsNullOrEmpty(cacheItem.Region) ? ('-' + cacheItem.Region) : string.Empty);
try
{
_lockProvider.Wait(lockKeyForAdd);
cacheManager.Add(cacheItem);
}
finally
{
_lockProvider.Release(lockKeyForAdd);
}
} ... where |
Thanks a lot. We implemented something similar by managing multiple semaphoreslim objects but LockProvider seems to be cleaner. |
Is this library still supported - from this conversation it sounds like there are some issues with no updates, etc.... |
Unfortunately it looks like this project is dead :( |
Any chance to get a new CacheManager version from the current changes in the "dev" branch? Especially the concurrency fix with f2d6e11 addresses a current production issue on our side.
The text was updated successfully, but these errors were encountered: