RE: [SMARTY-DEV] Re: [SMARTY] Cache cleanup

Nuts...well, what about the probability solution I suggested earlier? (cache cleanup fired at some % probability on every Smarty invocation ala PHP gc_probability). Then there would be random slowdowns for the people using it, but that would be the price for letting Smarty handle it. > -----Original Message----- > From: Monte Ohrt [mailto:monte@ispi.net] > Sent: Monday, June 17, 2002 9:37 AM > To: Monte Ohrt > Cc: Ivo Jansch; smarty-dev@lists.php.net > Subject: Re: [SMARTY-DEV] Re: [SMARTY] Cache cleanup > > > It seems that register_shutdown_function() is broken. We had > better not > rely on it. > > http://bugs.php.net/bug.php?id=15209 > > Monte Ohrt wrote: > > It looks like register_shutdown_function() might do the > trick for us > > anyways (?) So no need for an external script. > > > > > > http://www.php.net/manual/en/function.register-shutdown-function.php > > > > However, I see that the behavior isn't correct on Apache > for windows > > (see the second user contributed note) > > > > Monte > > > > Ivo Jansch wrote: > > > >> (I'm moving this thread to the dev list now) > >> > >> Monte Ohrt wrote: > >> > >>> The external file has to know your environment: where > template_dir > >>> and cache_dir is for example. It basically needs the > smarty object > >>> passed to it, so it would be better to include the script > and call a > >>> function. But then we're back to the processing time issue. > >> > >> > >> > >> You could also pass these as parameters to the external script. > >> > >> What also might be a solution is to create a cronscript > example that > >> you distribute with Smarty. > >> > >> But ofcourse, if Smarty could handle it, that would be > nicer (as long > >> as performance isn't affected). > >> > > > > > > > > -- > Monte Ohrt <monte@ispi.net> > Director of Technology, ispi Inc. > > > -- > Smarty Development Mailing List (http://smarty.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >