[RFC] advance sample on internals rewrite

book/internals.rst

@@ -44,6 +44,10 @@ variables:
   :class:`Symfony\\Component\\HttpFoundation\\SessionStorage\\SessionStorageInterface`
   interface abstract session management ``session_*()`` functions.
 
+.. note::
+
+    Read more about the :doc:`HttpFoundation Component </components/http_foudation/introduction>`.
+
 ``HttpKernel`` Component
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -58,6 +62,7 @@ Dependency Injection component and a powerful plugin system (bundles).
 
 .. seealso::
 
+    Read more about the :doc:`HttpKernel Component </components/http_kernel/introduction>`.
     Read more about :doc:`Dependency Injection </book/service_container>` and
     :doc:`Bundles </cookbook/bundles/best_practices>`.
 
@@ -234,6 +239,7 @@ add the following code at the beginning of your listener method::
     :doc:`Event Dispatcher Component Documentation</components/event_dispatcher/introduction>`
     section first.
 
+
 .. index::
    single: Event; kernel.request
 
@@ -256,6 +262,10 @@ uses a :class:`Symfony\\Component\\Routing\\RouterInterface` object to match
 the ``Request`` and determine the Controller name (stored in the
 ``_controller`` ``Request`` attribute).
 
+.. seealso::
+
+    Read more on the :ref:`kernel.request event <component-http-kernel-kernel-request>`.
+
 .. index::
    single: Event; kernel.controller
 
@@ -278,6 +288,10 @@ to modify the controller that should be executed::
         $event->setController($controller);
     }
 
+.. seealso::
+
+    Read more on the :ref:`kernel.controller event <component-http-kernel-kernel-controller>`.
+
 .. index::
    single: Event; kernel.view
 
@@ -307,6 +321,10 @@ The value returned by the Controller is accessible via the
         $event->setResponse($response);
     }
 
+.. seealso::
+
+    Read more on the :ref:`kernel.view event <component-http-kernel-kernel-view>`.
+
 .. index::
    single: Event; kernel.response
 
@@ -340,6 +358,24 @@ The ``FrameworkBundle`` registers several listeners:
   ``Surrogate-Control`` HTTP header when the Response needs to be parsed for
   ESI tags.
 
+.. seealso::
+
+    Read more on the :ref:`kernel.response event <component-http-kernel-kernel-response>`.
+
+.. index::
+   single: Event; kernel.terminate
+
+``kernel.terminate`` Event
+..........................
+
+.. versionadded:: 2.1
+    The ``kernel.terminate`` event is new since Symfony 2.1.
+
+.. seealso::
+
+    Read more on the :ref:`kernel.terminate event <component-http-kernel-kernel-terminate>`.
+
+
 .. index::
    single: Event; kernel.exception
 
@@ -383,6 +419,10 @@ and set a new ``Exception`` object, or do nothing::
 
         return new Response('Error', 404 /* ignored */, array('X-Status-Code' => 200));
 
+.. seealso::
+
+    Read more on the :ref:`kernel.exception event <component-http-kernel-kernel-exception>`.
+
 .. index::
    single: Event Dispatcher
 

components/http_kernel/introduction.rst

@@ -259,6 +259,8 @@ will be called after another event - ``kernel.controller`` - is dispatched.
     There are also a few other variations on the above process (e.g. if
     you're registering your controllers as services).
 
+.. _component-http-kernel-kernel-controller:
+
 3) The ``kernel.controller`` event
 ----------------------------------
 
@@ -444,6 +446,8 @@ method, which sends the headers and prints the ``Response`` content.
     serializes the current user's information into the
     session so that it can be reloaded on the next request. 
 
+.. _component-http-kernel-kernel-terminate:
+
 8) The ``kernel.terminate`` event
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~