On Sun, Jul 25, 2010 at 2:40 PM, Lukas Kahwe Smith <[email protected]> wrote: > actually it seems calling session_write_close() supposedly fixes the chicken > and egg issues. see the warning boxes on: > http://php.net/manual/en/function.session-set-save-handler.php
Yes that works if you use the stock session stuff or a register a custom session handler, but if you create a completely new implementation on the side, then I think you'd have to call your flush method before. Anyway it's not too hard you just need a reference to the session in the response. The (dis?)advantage of doing that is also that if you put a die(); or have an unhandled exception killing the request, the response won't be called, so the session isn't flushed with potentially-corrupted data.. Can be useful for debugging, but I guess it can also cause WTF's :) Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- 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
