Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:34889 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45976 invoked by uid 1010); 23 Jan 2008 18:41:28 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 45961 invoked from network); 23 Jan 2008 18:41:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jan 2008 18:41:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=rose.andrew@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rose.andrew@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.179 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rose.andrew@gmail.com X-Host-Fingerprint: 209.85.146.179 wa-out-1112.google.com Received: from [209.85.146.179] ([209.85.146.179:22487] helo=wa-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DC/89-17042-65A87974 for ; Wed, 23 Jan 2008 13:41:28 -0500 Received: by wa-out-1112.google.com with SMTP id l24so5586726waf.17 for ; Wed, 23 Jan 2008 10:41:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=+af8QzYjPTCNxEqh8X+uXptu4dYqWFto9IN9qevwoVI=; b=TX1IF6vX6QganoqBmQ85ZSI0cOi+CaV4pUtTcodmlb9LQIZhjrTXWy0Zh4UuGDKCsNXJGOwFznTz4N92rIgImunzNrAiQjxJUgXeacdFOVjtqL3pJxBArXMljVcIeQsm1yzOS4IZCVqHNQyiYOpkZRxaF+UFhU/ZvbaRb98EnWM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=vwtArowLgMybAc2mWuLRsUZpGVM3Qq4urw46LSTvepw8qKpT82Vi3LuynTPMSleBBYGIRXd8WTi0FwzShjTvELZbkoPav9oAKJL5VxHa4SgCvSR+nKJXI3QEUOz/9FgVzTEFfMNycBnb6QeRn0mAIvwYc34MZ15V0Y/eZwdTOqo= Received: by 10.114.209.1 with SMTP id h1mr1149046wag.115.1201113684225; Wed, 23 Jan 2008 10:41:24 -0800 (PST) Received: by 10.115.32.8 with HTTP; Wed, 23 Jan 2008 10:41:24 -0800 (PST) Message-ID: Date: Wed, 23 Jan 2008 18:41:24 +0000 To: "internals Mailing List" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: CLI SAPI/PHP Changes From: rose.andrew@gmail.com ("Andrew Rose") 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