MVC关系流程

http://ruby.railstutorial.org/chapters/a-demo-app.html?version=3.2#sec-planning_the_application

1.The browser issues a request for the /users URI.

2.Rails routes /users to the index action in the Users controller.
3.The index action asks the User model to retrieve all users (User.all).
4.The User model pulls all the users from the database.
5.The User model returns the list of users to the controller.
6.The controller captures the users in the @users variable, which is passed to the indexview.
7.The view uses embedded Ruby to render the page as HTML.

8.The controller passes the HTML back to the browser.3

         We start with a request issued from the browser—i.e., the result of typing a URI in the address bar or clicking on a link (Step 1 in Figure 2.11). This request hits the Rails router (Step 2), which dispatches to the proper controller action based on the URI (and, as we’ll see in Box 3.2, the type of request). The code to create the mapping of user URIs to controller actions for the Users resource appears in Listing 2.2; this code effectively sets up the table of URI/action pairs seen in Table 2.1. (The strange notation :users is a symbol, which we’ll learn about in Section 4.3.3.)

Example variable and class names Variables Constants and Local Global Instance Class Class Names name $debug @name @@total PI fishAndChips $CUSTOMER @point_1 @@symtab FeetPerMile x_axis $_ @X @@N String thx1138 $plan9 @_ @@x_pos MyClass _26 $Global @plan9 @@SINGLE Jazz_Song