Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 64eda65

Browse filesBrowse files
javiereguiluzjaviereguiluz
committed
minor #9253 Updated HttpKernel component diagrams (javiereguiluz)
This PR was squashed before being merged into the 2.7 branch (closes #9253). Discussion ---------- Updated HttpKernel component diagrams Commits ------- 1f896cf Updated HttpKernel component diagrams
2 parents 3042788 + 1f896cf commit 64eda65
Copy full SHA for 64eda65
Expand file treeCollapse file tree

17 files changed

+19
-32
lines changed

‎_images/components/http_kernel/01-workflow.png

Copy file name to clipboard
-123 KB
Binary file not shown.

‎_images/components/http_kernel/02-kernel-request.png

Copy file name to clipboard
-119 KB
Binary file not shown.

‎_images/components/http_kernel/03-kernel-request-response.png

Copy file name to clipboard
-119 KB
Binary file not shown.

‎_images/components/http_kernel/04-resolve-controller.png

Copy file name to clipboard
-118 KB
Binary file not shown.

‎_images/components/http_kernel/06-kernel-controller.png

Copy file name to clipboard
-121 KB
Binary file not shown.

‎_images/components/http_kernel/07-controller-arguments.png

Copy file name to clipboard
-122 KB
Binary file not shown.

‎_images/components/http_kernel/08-call-controller.png

Copy file name to clipboard
-122 KB
Binary file not shown.

‎_images/components/http_kernel/09-controller-returns-response.png

Copy file name to clipboard
-123 KB
Binary file not shown.

‎_images/components/http_kernel/10-kernel-view.png

Copy file name to clipboard
-121 KB
Binary file not shown.

‎_images/components/http_kernel/11-kernel-exception.png

Copy file name to clipboard
-123 KB
Binary file not shown.

‎_images/components/http_kernel/http-workflow-exception.svg

Copy file name to clipboardExpand all lines: _images/components/http_kernel/http-workflow-exception.svg
+1Lines changed: 1 addition & 0 deletions
Loading

‎_images/components/http_kernel/http-workflow-subrequest.svg

Copy file name to clipboardExpand all lines: _images/components/http_kernel/http-workflow-subrequest.svg
+1Lines changed: 1 addition & 0 deletions
Loading

‎_images/components/http_kernel/http-workflow.svg

Copy file name to clipboardExpand all lines: _images/components/http_kernel/http-workflow.svg
+1Lines changed: 1 addition & 0 deletions
Loading

‎_images/components/http_kernel/request-response-flow.png

Copy file name to clipboard
-327 KB
Binary file not shown.

‎_images/components/http_kernel/sub-request.png

Copy file name to clipboard
-125 KB
Binary file not shown.

‎_images/sources/http_kernel/http-workflow.dia

Copy file name to clipboard
3.7 KB
Binary file not shown.

‎components/http_kernel.rst

Copy file name to clipboardExpand all lines: components/http_kernel.rst
+16-32Lines changed: 16 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,14 @@ The Workflow of a Request
2727
Every HTTP web interaction begins with a request and ends with a response.
2828
Your job as a developer is to create PHP code that reads the request information
2929
(e.g. the URL) and creates and returns a response (e.g. an HTML page or JSON string).
30+
This is a simplified overview of the request workflow in Symfony applications:
3031

31-
.. image:: /_images/components/http_kernel/request-response-flow.png
32-
:align: center
32+
#. The **user** asks for a **resource** in a **browser**;
33+
#. The **browser** sends a **request** to the **server**;
34+
#. **Symfony** gives the **application** a **Request** object;
35+
#. The **application** generates a **Response** object using the data of the **Request** object;
36+
#. The **server** sends back the **response** to the **browser**;
37+
#. The **browser** displays the **resource** to the **user**.
3338

3439
Typically, some sort of framework or system is built to handle all the repetitive
3540
tasks (e.g. routing, security, etc) so that a developer can easily build
@@ -62,8 +67,9 @@ the concrete implementation of :method:`HttpKernelInterface::handle() <Symfony\\
6267
defines a workflow that starts with a :class:`Symfony\\Component\\HttpFoundation\\Request`
6368
and ends with a :class:`Symfony\\Component\\HttpFoundation\\Response`.
6469

65-
.. image:: /_images/components/http_kernel/01-workflow.png
66-
:align: center
70+
.. raw:: html
71+
72+
<object data="../_images/components/http_kernel/http-workflow.svg" type="image/svg+xml"></object>
6773

6874
The exact details of this workflow are the key to understanding how the kernel
6975
(and the Symfony Framework or any other library that uses the kernel) works.
@@ -138,9 +144,6 @@ layer that denies access).
138144
The first event that is dispatched inside :method:`HttpKernel::handle <Symfony\\Component\\HttpKernel\\HttpKernel::handle>`
139145
is ``kernel.request``, which may have a variety of different listeners.
140146

141-
.. image:: /_images/components/http_kernel/02-kernel-request.png
142-
:align: center
143-
144147
Listeners of this event can be quite varied. Some listeners - such as a security
145148
listener - might have enough information to create a ``Response`` object immediately.
146149
For example, if a security listener determined that a user doesn't have access,
@@ -150,9 +153,6 @@ to the login page or a 403 Access Denied response.
150153
If a ``Response`` is returned at this stage, the process skips directly to
151154
the :ref:`kernel.response <component-http-kernel-kernel-response>` event.
152155

153-
.. image:: /_images/components/http_kernel/03-kernel-request-response.png
154-
:align: center
155-
156156
Other listeners simply initialize things or add more information to the request.
157157
For example, a listener might determine and set the locale on the ``Request``
158158
object.
@@ -205,9 +205,6 @@ to your application. This is the job of the "controller resolver" - a class
205205
that implements :class:`Symfony\\Component\\HttpKernel\\Controller\\ControllerResolverInterface`
206206
and is one of the constructor arguments to ``HttpKernel``.
207207

208-
.. image:: /_images/components/http_kernel/04-resolve-controller.png
209-
:align: center
210-
211208
Your job is to create a class that implements the interface and fill in its
212209
two methods: ``getController()`` and ``getArguments()``. In fact, one default
213210
implementation already exists, which you can use directly or learn from:
@@ -280,9 +277,6 @@ some part of the system that needs to be initialized after certain things
280277
have been determined (e.g. the controller, routing information) but before
281278
the controller is executed. For some examples, see the Symfony section below.
282279

283-
.. image:: /_images/components/http_kernel/06-kernel-controller.png
284-
:align: center
285-
286280
Listeners to this event can also change the controller callable completely
287281
by calling :method:`FilterControllerEvent::setController <Symfony\\Component\\HttpKernel\\Event\\FilterControllerEvent::setController>`
288282
on the event object that's passed to listeners on this event.
@@ -314,9 +308,6 @@ should be passed to that controller. Exactly how this is done is completely
314308
up to your design, though the built-in :class:`Symfony\\Component\\HttpKernel\\Controller\\ControllerResolver`
315309
is a good example.
316310

317-
.. image:: /_images/components/http_kernel/07-controller-arguments.png
318-
:align: center
319-
320311
At this point the kernel has a PHP callable (the controller) and an array
321312
of arguments that should be passed when executing that callable.
322313

@@ -345,9 +336,6 @@ of arguments that should be passed when executing that callable.
345336

346337
The next step is simple! ``HttpKernel::handle()`` executes the controller.
347338

348-
.. image:: /_images/components/http_kernel/08-call-controller.png
349-
:align: center
350-
351339
The job of the controller is to build the response for the given resource.
352340
This could be an HTML page, a JSON string or anything else. Unlike every
353341
other part of the process so far, this step is implemented by the "end-developer",
@@ -357,9 +345,6 @@ Usually, the controller will return a ``Response`` object. If this is true,
357345
then the work of the kernel is just about done! In this case, the next step
358346
is the :ref:`kernel.response <component-http-kernel-kernel-response>` event.
359347

360-
.. image:: /_images/components/http_kernel/09-controller-returns-response.png
361-
:align: center
362-
363348
But if the controller returns anything besides a ``Response``, then the kernel
364349
has a little bit more work to do - :ref:`kernel.view <component-http-kernel-kernel-view>`
365350
(since the end goal is *always* to generate a ``Response`` object).
@@ -384,9 +369,6 @@ another event - ``kernel.view``. The job of a listener to this event is to
384369
use the return value of the controller (e.g. an array of data or an object)
385370
to create a ``Response``.
386371

387-
.. image:: /_images/components/http_kernel/10-kernel-view.png
388-
:align: center
389-
390372
This can be useful if you want to use a "view" layer: instead of returning
391373
a ``Response`` from the controller, you return data that represents the page.
392374
A listener to this event could then use this data to create a ``Response`` that
@@ -515,8 +497,9 @@ function is wrapped in a try-catch block. When any exception is thrown, the
515497
``kernel.exception`` event is dispatched so that your system can somehow respond
516498
to the exception.
517499

518-
.. image:: /_images/components/http_kernel/11-kernel-exception.png
519-
:align: center
500+
.. raw:: html
501+
502+
<object data="../_images/components/http_kernel/http-workflow-exception.svg" type="image/svg+xml"></object>
520503

521504
Each listener to this event is passed a :class:`Symfony\\Component\\HttpKernel\\Event\\GetResponseForExceptionEvent`
522505
object, which you can use to access the original exception via the
@@ -660,8 +643,9 @@ a page instead of a full page. You'll most commonly make sub-requests from
660643
your controller (or perhaps from inside a template, that's being rendered by
661644
your controller).
662645

663-
.. image:: /_images/components/http_kernel/sub-request.png
664-
:align: center
646+
.. raw:: html
647+
648+
<object data="../_images/components/http_kernel/http-workflow-subrequest.svg" type="image/svg+xml"></object>
665649

666650
To execute a sub request, use ``HttpKernel::handle()``, but change the second
667651
argument as follows::

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.