The document discusses ActionController in Ruby on Rails, which handles routing requests and sending responses by coordinating with models and views. It explains that Rails uses conventions like automatically routing GET requests to index actions, while Sinatra requires manually defining routes. CRUD actions for creating, reading, updating, and deleting data are covered. Filters and additional topics like sessions and rendering formats are also mentioned.

1. ActionController
by these guys & gal
Stephen(itis) Fab(ulous) (Toyota)Avalon
Phase 3 @devbootcamp Spring 2013
Monday, May 13, 13

2. What is ActionController?
MVC
Monday, May 13, 13

3. Like a switchboard
operatorRoutes
Controller
Monday, May 13, 13

4. Differences
• Route is included and defined
• View is defined by user
• Manually created
RailsSinatra
• Route is not included
• Rendered view is defined by
convention
• Actions can be automatically
generated by scaffolding
Monday, May 13, 13

5. So where are the routes
and views?
get ‘/posts’ => post#index
app/views/posts/index.html.erb
/app/config/routes.rb
Monday, May 13, 13

6. Convention over
configuration
• With Sinatra you are free to name and
define your controller actions/routes
• examples:
• get “/showindex” or post “/creatething”
• “In Rails there should be no guessing to what a
controller action is doing” - Shadi
Monday, May 13, 13

7. CRUD ACTIONS
• CREATE
• READ
• UPDATE
• DESTROY
Monday, May 13, 13

8. Controller:
light on logic
Monday, May 13, 13

9. READ
Monday, May 13, 13

10. CREATE
Monday, May 13, 13

11. UPDATE
Monday, May 13, 13

12. DESTROY
Monday, May 13, 13

13. Filters
Monday, May 13, 13

14. Some more for you
to explore
• Sessions
• Flashes
• Rendering xml and json
Monday, May 13, 13

15. Questions
?Monday, May 13, 13