Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:28343 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5708 invoked by uid 1010); 15 Mar 2007 11:36:15 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 5693 invoked from network); 15 Mar 2007 11:36:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2007 11:36:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=markus@fischer.name; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=markus@fischer.name; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fischer.name from 213.46.255.15 cause and error) X-PHP-List-Original-Sender: markus@fischer.name X-Host-Fingerprint: 213.46.255.15 viefep13-int.chello.at Solaris 10 (beta) Received: from [213.46.255.15] ([213.46.255.15:64686] helo=viefep11-int.chello.at) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FF/E9-24282-AAF29F54 for ; Thu, 15 Mar 2007 06:36:13 -0500 Received: from genuine ([213.47.89.232]) by viefep11-int.chello.at (InterMail vM.6.01.05.04 201-2131-123-105-20051025) with ESMTP id <20070315113607.XIQI12094.viefep11-int.chello.at@genuine>; Thu, 15 Mar 2007 12:36:07 +0100 Received: from [213.164.23.137] (helo=[10.15.10.17]) by genuine with esmtpa (Exim 4.50) id 1HRo9X-0005v7-AS; Thu, 15 Mar 2007 12:29:55 +0100 Message-ID: <45F92FA5.4060708@fischer.name> Date: Thu, 15 Mar 2007 12:36:05 +0100 User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: RQuadling@GoogleMail.com CC: internals References: <10845a340703140437q519bd232sc9b7dca53cef1e91@mail.gmail.com> <45F84785.9030304@fischer.name> <10845a340703150215v1dfe329ev8aaff25e3fcb5cbf@mail.gmail.com> In-Reply-To: <10845a340703150215v1dfe329ev8aaff25e3fcb5cbf@mail.gmail.com> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0 X-Spam-Level: / X-Spam-Report: Spam detection software, running on the system "genuine", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Richard, Richard Quadling wrote: > I feel there are 2 things to be considered with your suggestion. > > 1 - It doesn't matter what the server side handler is > (files/user/sqlite/mm/etc), session data is not stored until you do a > session_write_close(). So for a separate process to have access to the > data, the session must be closed. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- Subject: Re: [PHP-DEV] A request for code change : Repeated opening and closing the session leads to a LOT of Set-Cookie headers. From: markus@fischer.name (Markus Fischer) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Richard, Richard Quadling wrote: > I feel there are 2 things to be considered with your suggestion. > > 1 - It doesn't matter what the server side handler is > (files/user/sqlite/mm/etc), session data is not stored until you do a > session_write_close(). So for a separate process to have access to the > data, the session must be closed. Yes, that's true. > 2 - For the main process to update the session, a session_start() is > required which generates the Set-Cookie header. Maybe I misunderstand your code examples, but I thought that the long running process is the on with the UpdateSession() calls. So successively calling UpdateSession() generated successive Cookie headers sent to the browser in turn creating the IE specific problems. So, my suggestion was: you don't need to call session_start() inside UpdateSession(), because upon the first session_start() you know the session ID and therefore can update the database inside UpdateSession() without having to use the PHP functions, thus avoiding the particular problematic areas in the C code. However, this does not judge in anyway your proposal for the patch. - - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF+S+l1nS0RcInK9ARAuKyAKCYsIWc98KLgOgq+MVGBCafL8l98wCg4Qz7 NXS95MxlJkL8h3EiGF4XTac= =43oX -----END PGP SIGNATURE-----