# Expiring fragments from runners: best practice?

**URL:** <https://www.ruby-forum.com/t/expiring-fragments-from-runners-best-practice/120138>\
**Category:** Rails\
**Created:** [November 14, 2007, 1:56am UTC](https://www.ruby-forum.com/t/expiring-fragments-from-runners-best-practice/120138 "2007-11-14T01:56:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlundigard](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e9a140/32.png) [@jlundigard](https://www.ruby-forum.com/u/jlundigard)\
**Post date:** [November 14, 2007, 1:56am UTC](https://www.ruby-forum.com/t/expiring-fragments-from-runners-best-practice/120138/1 "2007-11-14T01:56:34Z")

</div>

I’m working on a complicated fragment caching scheme using memcache and  
I’m hoping someone has experience expiring fragments from  
runner/background scripts. Since expire\_fragment has only  
controller/action scope, I was thinking of creating a cache controller  
and using ActionController::Integration::Session.new to run local  
requests from the runners to expire the fragments.

Is this overly complicated? Is there a better way to do this? Any  
advice would be appreciated.

Thanks,  
Andy