note 8276 deleted from Session handling functions by ronabop
| From: | ronabop@php.net | Date: | Wed, 06 Sep 2000 05:58:35 +0000 |
| Subject: | note 8276 deleted from Session handling functions by ronabop | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-4196@lists.php.net to get a copy of this message | ||
Has anyone used PHP4 sessions with frames. I tried and had random results with 4.0.1pl2. It writes
session rows in a database. For a few days it wrote the serialised values then stopped. There were
no changes to php.ini, sql or anything obviously to do with sessions.
I traced the session handler calls. This is something that is important for managing framed data and
could be added to the documentation.
(I thought of helping the doco team and tried looking for CVS for NT but did not find one.)
With 4 frames, I ended up with read 1, read 2, read3, write 1, read 4, write 2, write 3, write 4.
All 4 parts of the frame had the same session id and session record but overlapped reads and writes.
As it happens, my code does not depend on what way around the reads and writes occur. Your
application may not be so lucky.
Futher down the track, I will need to store state information per frame and thought of an easy way
to do it. As I have yet to type out the SQL, I am wondering what other people have used successfully
across multiple frames.
Are there any other traps for new players when using sessions with frames?