CLI SAPI/PHP Changes
| From: | Andrew Rose | Date: | Wed, 23 Jan 2008 18:41:24 +0000 |
| Subject: | CLI SAPI/PHP Changes | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-34889@lists.php.net to get a copy of this message | ||
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