Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28368
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 64.233.182.186 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=tnVMhZNfgNXl5PEAH0uimB0ye9lR/1b8K8TKPyiqJZfM+SjfJ+Z/tPuKXNEPkSav9icemwGd51nA7DIoNw0NRaVv4189I3f5KoHlC8DqbJEfScsr8ndQPZgcphalIdCbJZ2P+b1KTaOGMqNJhc9BebFiNKWl//cosU49R2tUsKE=
Message-ID: <10845a340703160328y3b87e4d4ubdef684326eff492@mail.gmail.com>
Date: Fri, 16 Mar 2007 10:28:26 +0000
Reply-To: RQuadling@GoogleMail.com
To: ceo@l-i-e.com
Cc: "Markus Fischer" <markus@fischer.name>, internals <internals@lists.php.net>
In-Reply-To: <49068.216.230.84.67.1173986475.squirrel@www.l-i-e.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <10845a340703140437q519bd232sc9b7dca53cef1e91@mail.gmail.com>
	 <45F84785.9030304@fischer.name>
	 <10845a340703150215v1dfe329ev8aaff25e3fcb5cbf@mail.gmail.com>
	 <49068.216.230.84.67.1173986475.squirrel@www.l-i-e.com>
Subject: Re: [PHP-DEV] A request for code change : Repeated opening and closing the session leads to a LOT of Set-Cookie headers.
From: rquadling@googlemail.com ("Richard Quadling")

On 15/03/07, Richard Lynch <ceo@l-i-e.com> wrote:
> I think you still need locking in PHP Userland for concurrent access
> to be meaningful to most developers...
>
> Otherwise you end up with a race condition in the session save handler.

As only 1 process can hold the session at a time and the main process
is constantly "letting go" by session_write_close(), other processes
are able to open/read/close (to get the current status) or
open/write/close (to tell the main process to abort).

Without the session_write_close() in the main process, the secondary
processes will wait either for the appropriate set_time_limit() or
until the main process script ends. Which is correct.

This is working very well for me now.

It was the extra Set-Cookie headers which screwed things up for IE. By
using ini_set('sessions.use_cookies', 0); immediately after the
session_start() in the main process, the problem has been solved. The
main process doesn't output any urls/forms/etc, so the session id is
not appended to any urls.

If the session cookie could be cached then that would be great, but I
need someone else to look at the supplied patch (I'm not that good
with PHP internals).

Richard.

-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"