If your concern is debugging, then you can just see the error logs of PHP, if you don't see the errors in the browser then you can check there.
We use it in fastcgi_finish_request() in prod with no problems so far, but you'll need PHP-FPM. On Apr 13, 2010, at 10:03 PM, Jordi Boggiano wrote: > On 13.04.2010 15:42, Ren wrote: >> Hi, >> >> Just wondering what the cons are to conditionally (if PHP is running >> as fastcgi) calling fastcgi_finish_request() [1] in Response::send(). >> >> Seems quite nice way to deferring some work that doesn't affect the >> response, until after the response has been sent to the client, >> without any down sides? > > That looks very interesting, but also quite dangerous in development, if > an error occurs within the shutdown code and fcgi has closed the pipe I > guess you wouldn't see it in the browser. Therefore I think it should > only be called if debug is false. Apart from that I totally approve. > > Cheers, > Jordi > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
