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
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.