Skip to content
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

Open
Lumbendil opened this issue Jul 19, 2013 · 4 comments
Open

Stampede protection on doctrine adapter #32

Lumbendil opened this issue Jul 19, 2013 · 4 comments

Comments

@Lumbendil
Copy link
Contributor

It think it'd be great if it was possible to define a stampede protection mechanism for the doctrine adapter.

@tedivm
Copy link
Member

tedivm commented Jul 22, 2013

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.

@Lumbendil
Copy link
Contributor Author

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?

@tedivm
Copy link
Member

tedivm commented Aug 8, 2013

Sorry for the delay on this- I was at Defcon over the weekend and am still catching up on my email.

@tedivm
Copy link
Member

tedivm commented May 16, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants