Re: Purging Expired Session Objects
| From: | Sascha Schumann | Date: | Sat, 09 Sep 2000 05:43:02 +0000 |
| Subject: | Re: Purging Expired Session Objects | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-15977@lists.php.net to get a copy of this message | ||
On Thu, 7 Sep 2000, Thies Arntzen wrote:
> On Thu, Sep 07, 2000 at 05:18:15PM +0200, Sascha Schumann wrote:
> > > how many people are interested in "how many old sessions have
> > > just been GC'ed?" - near to none! those how are would gladly
> > > call session_get_gc_count(). changing the call to
> > > php_errror() to SESSION(gc_count) = n would actually _increase_
> > > performance by a few cycles (only at ramdom times though;-)
> >
> > We are looking at it from different perspectives. Your
> > solution is slower, if the user has to make some additional
> > calls in each request.
>
> how many users _are_ interested in this warning? for the
> majority of the people it would be faster.
The session module has been used by hundreds of users for
months. Three people including you have complained about the
warning. I'll leave it as an exercise to the reader how you
got to the conclusion that you are talking for the majority.
> why - E_NOTICE should print out reproduceable mesages that
> might be of interest to the user IMHO.
This is not very constructive. IMHO a developer using
sessions in her project is interested in the status of the
modules she uses.
I'm still in favor of adding a new log-level which can be
selectively enabled (as with E_NOTICE). If you dislike that
proposal, I guess the current behaviour will stay.
- Sascha