| ActionMailer EDGE |
Action Mailer is a framework for designing email-service layers. These
layers are used to consolidate code for sending out forgotten passwords,
welcome wishes on signup, invoices for billing, and any other use case that
requires a written notification to either a person or another system.
|
| ActionPack EDGE |
Action Pack splits the response to a web request into a controller part
(performing the logic) and a view part (rendering a template). This
two-step approach is known as an action, which will normally create, read,
update, or delete (CRUD for short) some sort of model part (often backed by
a database) before choosing either to render a template or redirecting to
another action.
|
| ActiveRecord EDGE |
Active Record connects business objects and database tables to create a
persistable domain model where logic and data are presented in one
wrapping. It’s an implementation of the object-relational mapping
(ORM) pattern
by the same name as described by Martin Fowler:
|
| ActiveResource EDGE |
Active Resource (ARes) connects business objects and Representational State
Transfer (REST) web services. It implements object-relational mapping for
REST webservices to provide transparent proxying capabilities between a
client (ActiveResource) and a RESTful service (which is provided by Simply
RESTful routing in ActionController::Resources).
|
| ActiveSupport EDGE |
Active Support is a collection of various utility classes and standard
library extensions that were found useful for Rails. All these additions
have hence been collected in this bundle as way to gather all that sugar
that makes Ruby sweeter.
|
| Rails 2.0.2 |
Rails is a web-application and persistence framework that includes
everything needed to create database-backed web-applications according to
the Model-View-Control pattern of separation. This pattern splits the view
(also called the presentation) into "dumb" templates that are
primarily responsible for inserting pre-built data in between HTML tags.
The model contains the "smart" domain objects (such as Account,
Product, Person, Post) that holds all the business logic and knows how to
persist themselves to a database. The controller handles the incoming
requests (such as Save New Account, Update Product, Show Post) by
manipulating the model and directing data to the view.
|
<code/>and<pre/>for code samples.