diff options
| author | sandeepravi <sandeep.ravichandran@sourcebits.com> | 2011-12-06 17:50:16 +0530 |
|---|---|---|
| committer | sandeepravi <sandeep.ravichandran@sourcebits.com> | 2011-12-06 17:50:16 +0530 |
| commit | bc994470c49fb17a6f984513c1299b94616ab83f (patch) | |
| tree | 894bdf4c247481a3858714e80dac1eb9a4d07ee8 | |
| parent | 8a67b632ae320e1983d8170f9c348c5a6333c9af (diff) | |
| download | rails-bc994470c49fb17a6f984513c1299b94616ab83f.tar.gz rails-bc994470c49fb17a6f984513c1299b94616ab83f.tar.bz2 rails-bc994470c49fb17a6f984513c1299b94616ab83f.zip | |
Added wiki link to REST
| -rw-r--r-- | railties/guides/source/action_controller_overview.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/action_controller_overview.textile b/railties/guides/source/action_controller_overview.textile index a55b7ba762..965da9f7dc 100644 --- a/railties/guides/source/action_controller_overview.textile +++ b/railties/guides/source/action_controller_overview.textile @@ -16,7 +16,7 @@ h3. 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 straightforward as possible. -For most conventional {REST}[http://en.wikipedia.org/wiki/Representational_state_transfer]ful applications, the controller will receive the request (this is invisible to you as 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. +For most conventional <span><a href="http://en.wikipedia.org/wiki/Representational_state_transfer">REST</a>ful</span> applications, the controller will receive the request (this is invisible to you as 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 that data to the user, and it saves or updates data from the user to the model. |