from within the daemon triggers no reaction. Is there anyting I could
change in the parameters I could add that would fix it?
Using a sweeper is a problem because the daemon updates a lot of models
but the cache should only be expired when a full round of updating is
completed – not with every single update of every single db entry. Fro
this purpose I created a Model to count the rounds - and then trigger
cache expiration after each ‘create’ of this counter. But this counter
model is not updated from any controller in the application - which - as
far as I understand it - is required to make the sweeper work.
Any help would be greatly appreciated!
Any luck with finding a solution? I’m in the same situation and need
to be able to run expire_fragment manually from the model or daemon.
Would love to know if you found a work around.
On Sep 30, 12:37ï¿½am, Justus O. <rails-mailing-l…@andreas-
No, I didn’t find a way to expire the cache from the daemon. My
workaround is to just let the fragments expire automatically by setting
a shorter expiration time in the memcached.yml. (for example, ttl: 300)