You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So it would be possible to hook into the controller_front_send_response_after event, "finish" the request and then execute the index events which happened trough the current save of the request.
Possible downsides are problematic error handling.
The text was updated successfully, but these errors were encountered:
So it would be possible to hook into the controller_front_send_response_after event, "finish" the request
and then execute the index events which happened trough the current
save of the request.
Possible downsides are problematic error handling.
Reply to this email directly or view it on GitHub: #5
thanks to http://www.php.net/manual/en/function.fastcgi-finish-request.php we are able to execute longer running tasks after actually sending the response.
So it would be possible to hook into the controller_front_send_response_after event, "finish" the request and then execute the index events which happened trough the current save of the request.
Possible downsides are problematic error handling.
The text was updated successfully, but these errors were encountered: