-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Improve the docs about async processes #7151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub& 8000 rdquo;, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
tristanbes
added a commit
to tristanbes/symfony-docs
that referenced
this issue
Nov 22, 2016
…esponse Fixes symfony#7151 It confuses user that could be tempted to use the Asynchronous Process feature to achieve long running task after the Response is sent. The result is the following : from no code execution (if you send a Response really fast) to partial code execution
Fixed by #7159 upon approval |
xabbuh
added a commit
that referenced
this issue
Mar 13, 2017
…ive a response (tristanbes, javiereguiluz) This PR was merged into the 2.7 branch. Discussion ---------- [Process] Add explanation on how to make the Process survive a response Fixes #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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See symfony/symfony#20513 for the full details
The text was updated successfully, but these errors were encountered: