Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:34918 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24908 invoked by uid 1010); 24 Jan 2008 06:07:35 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 24893 invoked from network); 24 Jan 2008 06:07:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2008 06:07:35 -0000 X-Host-Fingerprint: 75.141.45.86 unknown Received: from [75.141.45.86] ([75.141.45.86:16318] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/37-17042-40B28974 for ; Thu, 24 Jan 2008 01:07:00 -0500 Message-ID: <88.37.17042.40B28974@pb1.pair.com> To: internals@lists.php.net Date: Wed, 23 Jan 2008 22:05:55 -0800 User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 75.141.45.86 Subject: Re: CLI SAPI/PHP Changes From: brian@zablocky.org (Brian Zablocky) Andrew Rose wrote: > Hi > > I'm looking into making a few changes to the PHP session code in > respect to the CLI SAPI. But before I did, I wanted to see if the > changes (patch) would be excepted (I really hate wasting my time). > The changes are as such: > > 1. Update the session code to suppress "headers already sent" warnings > when running via the CLI SAPI. > 2. Update the session_set_save_handler() functionality to persist past > session_destroy() ready for another session_start(). Maybe via a > flag? > > From what I have gathered, the CLI SAPI silently ignores headers, so > the fact is throws warnings seems superfluous. The session handler > persisting past a session_destroy() I'm just not sure about, so would > appreciate any heads up / advice. > > Both points have workarounds, but it would be nice to not have to > workaround them. > > Anyway, would these changes likely be accepted? > > cheers > Andrew Rose I obviously can't speak for the php team, but I have personally experienced item 1 and have had to code around it. I have no experience with item 2. --Brian Z