[#2002] Re-adding the caching information to the rendering a template without a controller doc

Author: weaverryan

cookbook/templating/render_without_controller.rst

@@ -57,8 +57,8 @@ template you've passed as the ``template`` default value.
 You can of course also use this trick when rendering embedded controllers
 from within a template. But since the purpose of rendering a controller from
 within a template is typically to prepare some data in a custom controller,
-this probably isn't useful, except to easily cache static partials, a feature
-which will become available in Symfony 2.2.
+this is probably only useful if you'd like to cache this page partial (see
+:ref:`cookbook-templating-no-controller-caching`).
 
 .. configuration-block::
 
@@ -71,3 +71,67 @@ which will become available in Symfony 2.2.
         <?php echo $view['actions']->render(
             $view['router']->generate('acme_privacy', array(), true)
         ) ?>
+
+.. _cookbook-templating-no-controller-caching:
+
+Caching the static Template
+---------------------------
+
+.. versionadded:: 2.2
+    The ability to cache templates rendered via ``FrameworkBundle:Template:template``
+    is new in Symfony 2.2.
+
+Since templates that are rendered in this way are typically static, it might
+make sense to cache them. Fortunately, this is easy! By configuring a few
+other variables in your route, you can control exactly how your page is cached:
+
+.. configuration-block::
+
+    .. code-block:: yaml
+
+        acme_privacy:
+            pattern: /privacy
+            defaults:
+                _controller: FrameworkBundle:Template:template
+                template: 'AcmeBundle:Static:privacy.html.twig'
+                maxAge: 86400
+                sharedMaxAge: 86400
+
+    .. code-block:: xml
+
+        <?xml version="1.0" encoding="UTF-8" ?>
+
+        <routes xmlns="http://symfony.com/schema/routing"
+            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+            xsi:schemaLocation="http://symfony.com/schema/routing http://symfony.com/schema/routing/routing-1.0.xsd">
+
+            <route id="acme_privacy" pattern="/privacy">
+                <default key="_controller">FrameworkBundle:Template:template</default>
+                <default key="template">AcmeBundle:Static:privacy.html.twig</default>
+                <default key="maxAge">86400</default>
+                <default key="sharedMaxAge">86400</default>
+            </route>
+        </routes>
+
+    .. code-block:: php
+
+        use Symfony\Component\Routing\RouteCollection;
+        use Symfony\Component\Routing\Route;
+
+        $collection = new RouteCollection();
+        $collection->add('acme_privacy', new Route('/privacy', array(
+            '_controller'  => 'FrameworkBundle:Template:template',
+            'template'     => 'AcmeBundle:Static:privacy.html.twig',
+            'maxAge'       => 86400,
+            'sharedMaxAge' => 86400,
+        )));
+
+        return $collection;
+
+The ``maxAge`` and ``sharedMaxAge`` values are used to modify the Response
+object created in the controller. For more information on caching, see
+:doc:`/book/http_cache`.
+
+There is also a ``private`` variable (not shown here). By default, the Response
+will be made public, as long as ``maxAge`` or ``sharedMaxAge`` are passed.
+If set to ``true``, the Response will be marked as private.