minor symfony#7159 [Process] Add explanation on how to make the Process survive a response (tristanbes, javiereguiluz)

xabbuh · xabbuh · commit 01ebdc3ef578 · 2017-03-13T09:59:27.000+01:00
This PR was merged into the 2.7 branch. Discussion ---------- [Process] Add explanation on how to make the Process survive a response Fixes symfony#7151 It clarifies the situation for users that could be tempted to use the asynchronous `Process` feature to achieve long running task after the Response is sent which won't work. It goes from no code execution (if you send a Response really fast) to partial code execution. Commits ------- cdf248c add a caution block about php-fpm pool 020f1b7 Fixed some syntax issues 64de236 Add explanation how to make the Process survive a response
diff --git a/components/process.rst b/components/process.rst
@@ -124,6 +124,25 @@ are done doing other stuff::
     which means that your code will halt at this line until the external
     process is completed.
 
+.. note::
+
+    If a ``Response`` is sent **before** what ``Process`` is running had a chance to complete,
+    the server process will be killed (depending on your OS). It means that your task
+    will be stopped right away. Running an asynchronous process is not the same than running
+    a processing surviving yourselves.
+
+    If you want your process to survive the request/response cycle, you could take
+    advantage of the ``kernel.terminate`` event, and run your command **synchronuously**
+    inside this event. Be aware that ``kernel.terminate`` is called only if you run ``PHP-FPM``.
+
+.. caution::
+
+    Beware also that if you do that, the said php process won't available to serve
+    any new request until the subprocess is finished, which means you can block your
+    FPM pool quickly if you're not careful enough.
+    That's why it generally way better to not do any fancy thing even after the request is sent
+    but prefer using a job queue.
+
 :method:`Symfony\\Component\\Process\\Process::wait` takes one optional argument:
 a callback that is called repeatedly whilst the process is still running, passing
 in the output and its type::
