Re: Purging Expired Session Objects
| From: | Sascha Schumann | Date: | Thu, 07 Sep 2000 15:18:15 +0000 |
| Subject: | Re: Purging Expired Session Objects | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-15730@lists.php.net to get a copy of this message | ||
> 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.
<insert usual blabla about "near to none" fake statements>
> > The default error_warning is E_ALL & ~E_NOTICE and that is good.
>
> i really want E_NOTICE to be shown - things like "Undefined
> variable" and "Undefined index" are very helpful messages
> when writing scripts. i think a lot of people do agree to me
> here. the number of sessions GC'ed is of no importance
> whatsoever to the normal script - only if you're debugging
> the session code itself this information has value.
Well, so create an E_CORE_NOTICE log level which is used by
the Zend core to report issues like the above. When it is
more fine-grained, you can select what you need.
- Sascha