From a2932784bb71e72a78c32819ebd7ed2bed551e3e Mon Sep 17 00:00:00 2001 From: Pratik Naik Date: Sun, 5 Oct 2008 22:16:26 +0100 Subject: Merge docrails --- railties/doc/guides/actioncontroller/introduction.txt | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 railties/doc/guides/actioncontroller/introduction.txt (limited to 'railties/doc/guides/actioncontroller/introduction.txt') diff --git a/railties/doc/guides/actioncontroller/introduction.txt b/railties/doc/guides/actioncontroller/introduction.txt new file mode 100644 index 0000000000..35540bbc09 --- /dev/null +++ b/railties/doc/guides/actioncontroller/introduction.txt @@ -0,0 +1,7 @@ +== What does a controller do? == + +Action Controller is the C in MVC. After routing has determined which controller to use for a request, your controller is responsible for making sense of the request and producing the appropriate output. Luckily, Action Controller does most of the groundwork for you and uses smart conventions to make this as straight-forward as possible. + +For most conventional RESTful applications, the controller will receive the request (this is invisible to the developer), fetch or save data from a model and use a view to create HTML output. If your controller needs to do things a little differently, that's not a problem, this is just the most common way for a controller to work. + +A controller can thus be thought of as a middle man between models and views. It makes the model data available to the view so it can display it to the user, and it saves or updates data from the user to the model. -- cgit v1.2.3