I want to create a very simple facebook application for my Rails app. At first since it is very simple, I created something in PHP, put it outside of the application space and set the callback URL to there. However, I would rather the facebook app live inside my Rails app (one reason is that so I can reuse views when necessary).
Because my facebook app will look much different and act pretty different from my Rails app, I need different views and controller actions talking to those views. My first instinct is to create a Facebook controller and somehow route all "facebook.my_domain.com" requests to the facebook controller. This will allow me to require facebook login for only requests to that controller and separate facebook app from the main app. I have read that a good method is to render different views based on the requested format but the issue is I don't want to do the same thing in the controller action if the request format is different. It seems ugly to interact with the model differently based on the request format in the controller action as opposed to mapping all requests to a Facebook controller based on the request format and interact with the model differently in the controller specific to Facebook.
Does this make sense or should I really try to not add a Facebook controller?