Permalink
Browse files

[glossary] Making the glossary sort by default and slightly modifying…

… the format so so that it would render correctly.
  • Loading branch information...
1 parent 6649191 commit a4105f40b71f927618e16252ef4723a18f134f8e @weaverryan weaverryan committed Feb 22, 2011
Showing with 7 additions and 6 deletions.
  1. +7 −6 glossary.rst
View
@@ -4,36 +4,37 @@ Glossary
========
.. glossary::
+ :sorted:
- Project
+ Project
A *Project* is a directory composed of an Application, a set of
bundles, vendor libraries, an autoloader, and web front controller
scripts.
- Application
+ Application
An *Application* is a directory containing the *configuration* for a
given set of Bundles.
- Bundle
+ Bundle
A *Bundle* is a structured set of files (PHP files, stylesheets,
JavaScripts, images, ...) that *implement* a single feature (a blog,
a forum, ...) and which can be easily shared with other developers.
- Front Controller
+ Front Controller
A *Front Controller* is a short PHP that lives in the web directory
of your project. Typically, *all* requests are handled by executing
the same front controller, whose job is to bootstrap the Symfony
application.
- Service
+ Service
A *Service* is a generic term for any PHP object that performs a
specific task. A service is usually used "globally", such as a database
connection object or an object that delivers email messages. In Symfony2,
services are often configured and retrieved from the service container.
An application that has many decoupled services is said to follow
a `service-oriented architecture`_.
- Service Container
+ Service Container
A *Service Container*, also known as a *Dependency Injection Container*,
is a special object that manages the instantiation of services inside
an application. Instead of creating services directly, the developer

0 comments on commit a4105f4

Please sign in to comment.