Re: Purging Expired Session Objects

On Thu, Sep 07, 2000 at 04:57:53PM +0200, Sascha Schumann wrote: > On Thu, 7 Sep 2000, Thies Arntzen wrote: > > > On Thu, Sep 07, 2000 at 02:31:27PM +0200, Sascha Schumann wrote: > > > > BTW: sascha - i'm not all that that happy with a notice that > > > > is generated at random times. do we really need it? > > > > > > If you can suggest a better way of recording this event, we might > > > evaluate changing this to something different. > > > > it's doesn't need to be logged by PHP - if the user want's to > > log it we should simply return the number (remembered in > > sessin_start) of GC'ed sessions thru a function. > > That's a kludge and just adds to the execution time. no - 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;-) > > 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. calling session_start() with @ would eliminate this vary random notice, but would also hide if there was a real problem starting the session. 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