-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Richard,
Richard Quadling wrote: > I feel there are 2 things to be considered with your suggestion. > > 1 - It doesn't matter what the server side handler is > (files/user/sqlite/mm/etc), session data is not stored until you do a > session_write_close(). So for a separate process to have access to the > data, the session must be closed. Yes, that's true. > 2 - For the main process to update the session, a session_start() is > required which generates the Set-Cookie header. Maybe I misunderstand your code examples, but I thought that the long running process is the on with the UpdateSession() calls. So successively calling UpdateSession() generated successive Cookie headers sent to the browser in turn creating the IE specific problems. So, my suggestion was: you don't need to call session_start() inside UpdateSession(), because upon the first session_start() you know the session ID and therefore can update the database inside UpdateSession() without having to use the PHP functions, thus avoiding the particular problematic areas in the C code. However, this does not judge in anyway your proposal for the patch. - - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF+S+l1nS0RcInK9ARAuKyAKCYsIWc98KLgOgq+MVGBCafL8l98wCg4Qz7 NXS95MxlJkL8h3EiGF4XTac= =43oX -----END PGP SIGNATURE----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
