Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52392
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        b=BaBXo9/u28Njw/q2bGdl4iMjUO6Nz+FQa0UK0fmvCC5H3oA1zW29M/DrOqSC+4b/Ce
         5h2kKXnW2KvLb2FllHgvGkqiNx9PmkQ0he0uro9NLyaieCYJm8RwsQQ6uYrA+Lq0mw2c
         qtkmoBTLecbDh2WzxZOIk6Ucs02/dyN+rNyi8=
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <4DD12989.7090602@thelounge.net>
References: <20110516133753.GA24346@phcomp.co.uk>
	<4DD12989.7090602@thelounge.net>
Date: Mon, 16 May 2011 15:50:58 +0200
Message-ID: <BANLkTinTr1Bb9HAange5LMcMU7F9B=TG8w@mail.gmail.com>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=0016e65b52f8f7f53f04a364f1ba
Subject: Re: [PHP-DEV] session_disconnect()
From: info@tyrael.hu (Ferenc Kovacs)

--0016e65b52f8f7f53f04a364f1ba
Content-Type: text/plain; charset=UTF-8

On Mon, May 16, 2011 at 3:41 PM, Reindl Harald <h.reindl@thelounge.net>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 means only that changes to $_SESSIOn are not available for other
> requests
>
> Am 16.05.2011 15:37, schrieb Alain Williams:
> > 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 side calls need a lot of work.
> >
> > May I suggest:
> >
> >     session_disconnect();
> >
> > This would, in effect, close the session file but leave $_SESSION. This
> would be easy to implement,
> > just call the second callback to session_set_save_handler().
> >
> > This is NOT quite the same as a session_end() function since that would
> presumably write the
> > (changed) contents of $_SESSION back to where ever. With
> session_disconnect() any changes made
> > to $_SESSION would be lost regardless of them being made before or after
> the call to session_disconnect().
> >
> > Another way of doing this would be to add an optional boolean argument to
> session_start() which
> > would load $_SESSION and then disconnect. This is more intrusive in that
> changes to any user
> > open functions (of session_set_save_handler()) would be needed. It might
> be a tiny bit faster
> > or neater.
> >
> >
> > I do not know how much of a speed improvement this would make to what
> sort of AJAX applications.
>
>
on a related note, could we fix http://bugs.php.net/bug.php?id=38104 ?
with that in mind, somebody could close and reopen the session
as necessary(with releasing and acquiring the lock properly).
personally I always went with the lock the whole session until the request
is complate, used the session_write_close to release the lock on the session
before the request ended, but never needed to re-open it after I closed.
but I can see why is the current behaviour is a PITA.

Tyrael

--0016e65b52f8f7f53f04a364f1ba--