The question is complicated because there are many alternatives, but the answer will depend on what you are trying to do.
Is context present in your model? Then you should use different models and different controllers.
Is context something other than REST actions? Add a custom REST action ( http://railscasts.com/episodes/35-custom-rest-actions ) with the appropriate route (it seems to me what you are trying to do here).
Are representations equivalent, only with different markup? You can use cells ( http://cells.rubyforge.org/ ) to distract your presentation template.
I would strongly oppose creating multiple actions if you do not want to break the RESTful state, but in the end it can also be a solution.
source share