I am working on re-writing my application based on what I learned in RailsConf 2009. I understand that Model, Controller and View are related. However, one thing I struggled with is the "correct" level for the controller.
If the Rails model displays (approximately) the database table ... And if the Rails View displays (approximately) the browser page ...
What does the Rails controller point to?
A controller is a means of connecting models (models) to View (s) using the logic, constraints and conditions of your decision.
So, I suppose it can display the brains of your decision.
, . , .
..... .
- , , . , , . , .
MVC , , . , ( ) , . , - , , , , , , .
, . - , . - , , , , " ", - , .
, "".
. (, ). - , , .
, - . , , , . .
URL-, RESTFUL-.
URL- .
MVC, , :
- ( )
- ( , )
, , "Get It", , . , "" , .
Source: https://habr.com/ru/post/1708700/More articles:Выполните .Select() в IQueryable со списком делегатов Func - genericsASP.Net Webparts: How to Hide a Web Part? - c #Каковы различия между программированием в ИТ-отделе и отделе разработки продукта? - development-environmentGet the window handle of the last activated window - c ++Break the long command line testing method - c ++mysql backup data comparison - databaseSimplification of expression - schemeНасколько релевантен Альянс OpenAjax для среднего веб-разработчика? - javascriptUsing WSDL to send and receive in C # - c #If you use Google Checkout, do you still need to use ActiveMerchant / Spree / some payment gateway in Rails? - ruby-on-railsAll Articles