Re: [SM-DEVEL] Re: [SM-USERS] Call to undefined function: session_write_close()

[Erin S. <si...@ha...>]

Jonathan Angliss said:

> What double login? You mean the one I fixed with the
> sqsession_destroy? Based on the comments on php.net that function is
> used for something else.
>
> ,----- [
> http://www.php.net/manual/en/function.session-write-close.php ]
> | Session data is usually stored after your script terminated
> | without the need to call session_write_close(), but as session
> | data is locked to prevent concurrent writes only one script
> | may operate on a session at any time.
> | When using framesets together with sessions you will
> | experience the frames loading one by one
> | due to this locking. You can reduce the time needed to load
> | all the frames by ending the session as soon as all changes
> | to session variables are done.
> `-----
>
> I think maybe a better look into what the function does, and how it
> is needed might be in order first. Based on what the docs say, it
> forces a premature writing of the session data file instead of at
> the end of script which is automatic. Not entirely sure why though.
>


I snipped that same paragraph out and posted it to the list awhile ago.

I think we need to examine our interaction with sessions in general.

Yes, it's good to cache things in the session, but because we use
frames, that can also cause contention on start up (which is pointed
out in your nicely snipped paragraph).

I also seem to remember session_write_close being added to force an
auto-started session to close so that we could load our classes
before session-start.

Erin
(sizzle)

--
'Waste of a good apple.' ~Samwise Gamgee
(ICQ: 36870353)