8000 outline implications of the kernel.terminate event · symfony/symfony-docs@b291d84 · GitHub
[go: up one dir, main page]

Skip to content

Commit b291d84

Browse files
committed
outline implications of the kernel.terminate event
1 parent e8964f4 commit b291d84

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

components/http_kernel/introduction.rst

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -472,6 +472,15 @@ you will trigger the ``kernel.terminate`` event where you can perform certain
472472
actions that you may have delayed in order to return the response as quickly
473473
as possible to the client (e.g. sending emails).
474474

475+
.. caution::
476+
477+
Internally, the HttpKernel makes use of the :phpfunction:`fastcgi_finish_request`
478+
PHP function. This means that, at the moment, only the `PHP FPM`_ server
479+
API is able to send a response to the client while the server's PHP process
480+
still performs some tasks. With all other server APIs, listeners to ``kernel.terminate``
481+
are still executed, but the response is not sent to the client until they
482+
are all completed.
483+
475484
.. note::
476485

477486
Using the ``kernel.terminate`` event is optional, and should only be
@@ -689,3 +698,4 @@ look like this::
689698
.. _reflection: http://php.net/manual/en/book.reflection.php
690699
.. _FOSRestBundle: https://github.com/friendsofsymfony/FOSRestBundle
691700
.. _`Create your own framework... on top of the Symfony2 Components`: http://fabien.potencier.org/article/50/create-your-own-framework-on-top-of-the-symfony2-components-part-1
701+
.. _`PHP FPM`: http://php.net/manual/en/install.fpm.php

0 commit comments

Comments
 (0)
0