mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Ruby on Rails
ed34652d1a
If you have existing Metals, you have a few options: * if your metal behaves like a middleware, add it to the middleware stack via config.middleware.use. You can use methods on the middleware stack to control exactly where it should go * if it behaves like a Rack endpoint, you can link to it in the router. This will result in more optimal routing time, and allows you to remove code in your endpoint that matches specific URLs in favor of the more powerful handling in the router itself. For the future, you can use ActionController::Metal to get a very fast controller with the ability to opt-in to specific controller features without paying the penalty of the full controller stack. Since Rails 3 is closer to Rack, the Metal abstraction is no longer needed. |
||
|---|---|---|
| actionmailer | ||
| actionpack | ||
| activemodel | ||
| activerecord | ||
| activeresource | ||
| activesupport | ||
| bin | ||
| ci | ||
| doc/template | ||
| railties | ||
| tools | ||
| .gitignore | ||
| Gemfile | ||
| load_paths.rb | ||
| rails.gemspec | ||
| RAILS_VERSION | ||
| Rakefile | ||
| release.rb | ||
| version.rb | ||