Re: Purging Expired Session Objects

From: Date: Thu, 07 Sep 2000 15:34:43 +0000
Subject: Re: Purging Expired Session Objects
References: 1 2  Groups: php.general 
Request: Send a blank email to php-general+get-15735@lists.php.net to get a copy of this message
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 (lets ignore tha slower/faster thing - we're talking about a few cycles). > > <insert usual blabla about "near to none" fake statements> i really dislike randown notices - they make no sense *plus* they make people use @ or even decrease their error_reporting level where it's not needed. > > > > 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. why - E_NOTICE should print out reproduceable mesages that might be of interest to the user IMHO. <repeating myself> generating random notices is confusing and will end up in people switching off PHP notices completely </repeating myself> - which is bad. why do we generate notices in the 1st place if your are _forced_ to switch them off? adding an .ini flag to have the session module spit out addtional debug stuff is fine by me - but this GC notice does not belong in there! tc > > - Sascha -- Thies C. Arntzen "One Big-Mac, Small Fries and a Coke!" Digital Collections Phone +49 40 235350 Fax +49 40 23535180 Hammerbrookstr. 93 20097 Hamburg / Germany

« previous php.general (#15735) next »