> > I think maybe you misunderstood me. This is a hosted service built around > > TT that we host for others. Since this is something that would obviously be > > an issue for anyone using TT to run a hosted service where you have multiple > > users, I thought it would be better to just add it to the core code instead > > of subclassing Provider.pm. > > It sounds like a good idea, provided it is optional. People who are > very concerned about performance wouldn't want the extra file access, > and are probably willing to restart mod_perl when they change their > templates. > > By the way, does your change work for the on-disk cache as well? I > remember that being kind of annoying, how I would have to clear that out > manually when I launched a new set of templates. > > - Perrin > > I'm currently trying to think up the best solution to handle both the memory cache and the disk cache that would work for the widest variety of situations. I know that a lot of people wont' want the extra stat when just accessing the memory cache so would obviously have to be an option. For the disk cache there seems to be a few ways to handle it. You could either have a function that deletes the entire disk cache or specific compiled files on demand, or let the system remove them over time as it finds that the corresponding template doesnt' exist. Need to think about this some more though.
Chris _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
