Am 16.05.2011 15:50, schrieb Alain Williams:
> On Mon, May 16, 2011 at 03:41:29PM +0200, Reindl Harald wrote:
>> There is no function needed if you use
>> http://php.net/manual/de/function.session-write-close.php
>> like others do since ten years :-)
>
> But that writes $_SESSION back. I am loo
On Mon, May 16, 2011 at 3:41 PM, Reindl Harald wrote:
> There is no function needed if you use
> http://php.net/manual/de/function.session-write-close.php
> like others do since ten years :-)
>
> if you know that you no longer write to the session use it
> this does not mean $_SESSION is lost
> it
On Mon, May 16, 2011 at 03:41:29PM +0200, Reindl Harald wrote:
> There is no function needed if you use
> http://php.net/manual/de/function.session-write-close.php
> like others do since ten years :-)
But that writes $_SESSION back. I am looking to optimise the case when you know
that there will
There is no function needed if you use
http://php.net/manual/de/function.session-write-close.php
like others do since ten years :-)
if you know that you no longer write to the session use it
this does not mean $_SESSION is lost
it means only that changes to $_SESSIOn are not available for other r
I am working on some AJAX callbacks. These need to open the session, get hold
of stuff in $_SESSION
and that is it ... they won't be changing the session data. The trouble is that
because the
session file is locked the Asynchronicity of AJAX is reduced a bit, especially
if some of the
server sid
