How/when the 'after_filter' works/runs?

Question

I am using Ruby on Rails 3.1 and I would like to know (for performance reasons) whether or not the after_filter runs after that view files are rendered. Th

Answer 1

You have to be aware that a request to your server is fully consistent and runs in its own thread.

If you put code in an after_filter, this will delay the whole request: to sum up badly, if the thread is alive, the page is not delivered.

That's why you find great plugins like DelayedJob and Resque, they work in a parallel processes and won't affect your app.

---

To answer your original question , after_filter are triggered after the view has been processed.

This is sometimes a hassle that's why people created some before_render filters.

Answer 2

after_filter is run after the content has been generated, but before it's been sent to the client. You can verify this is so because you have access to the completely-generated response data in the response method of your controller in any after_filter.

After_filters are inappropriate places to put long running tasks as they will definitely impact the users' experience. Consider instead using the after_filter to kick off a long running delayed_job or resque task to perform your background work instead.