-
Notifications
You must be signed in to change notification settings - Fork 6
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
Improvements #127
base: main
Are you sure you want to change the base?
Improvements #127
Conversation
Signed-off-by: Matthias Bertschy <[email protected]>
Signed-off-by: Matthias Bertschy <[email protected]>
Summary:
|
1 similar comment
Summary:
|
Signed-off-by: Matthias Bertschy <[email protected]>
|
||
cacheClient, err := cache.NewClient( | ||
cache.ClientWithAdapter(memcached), | ||
cache.ClientWithTTL(10*time.Minute), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
obviously this needs to be set lower, or we should check how to invalidate cache
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes indeed
Summary:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have looked into the http-cache
package. My main concern is the lack of cache invalidation. I don't see it invalidates cache items on the PUSH
/PUT
/UPDATE
/DELETE
methods. Either we fork and implement this, or need to find another solution because this implementation leads to inconsistency.
No description provided.