Re: [SMARTY-DEV] Re: speed improvement idea: path caching

--- Monte Ohrt <monte@ispi.net> wrote: > After further thinking, maybe a separate path cache per call to > display() or fetch() would work best. Therefore we have a definitive > set of paths to load, thus we don't have to load _every_ path just to > display one set of files. This also alleviates the need for pruning. > So if I load $smarty->display('index.tpl'); this will have it's own > path cache file, containing the paths to every compiled file and > plugin used for this page. Even dynamic things will work fine like > {include file=$my_path}, it will just add the new path to the cache > file when it encounters a new one. Monte I like your thinking. Would this be embedded into the head of the compiled template? Or kept in a separate file to speed recompiles as well? The latter option may again lead to invalid entries in the path cache -- but forcing a path cache rebuild during compilation can be parameter controlled if that is a problem. I've been trying to get the current CVS to work on my win2k system to no avail. The entries in the path cache look suspicious. I'll try again tommorow. xo boots ps. the new resource naming looks nice, though it is getting hard to keep up with all of the changes! __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com