-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Stampede protection on doctrine adapter #32
Comments
Right now the different invalidation methods are set as part of the Item->get functions, which means it can't easily be changed by a parameter call. Stash 0.11.1 is going to change how stampede protection works, from an API perspective, and will make this a lot easier to handle. I'm hoping to have this built out in the next week and a half, at which point this ticket will be a quick addition. |
You mentioned Stash 0.11 changing how stampede protection works, can you point me to some issues which show what you have in mind so I can help implement it? |
Sorry for the delay on this- I was at Defcon over the weekend and am still catching up on my email. |
Super late answer on this one. The next release changes the default invalidation method to precompute, which is what I imagine 99% of people will want. I'm planning on making some configuration related changes in the release after that, which should include this. |
It think it'd be great if it was possible to define a stampede protection mechanism for the doctrine adapter.
The text was updated successfully, but these errors were encountered: