Just trying to change the topic name... On Sep 26, 2008, at 2:42 PM, Kris Wallsmith wrote:
> > Maybe I framed this wrong... > > I'm suggesting we extend the config cache to use any of the sfCache > implementations that come with the framework? That way devs can use > APC, memcache, or no cache if they so choose. > > Kris > > On Sep 26, 11:10 am, Fabien Potencier <[EMAIL PROTECTED] > project.com> wrote: >> The problem is that the symfony autoloading mecanism allows you to >> have >> the structure you want for your classes. So, it needs to parse all >> the >> files to provide autoloading. We must cache the result. If not, the >> response time will be too much, even for the dev env. >> >> So, you "only" need to clear your cache when you add a new class. >> >> Fabien >> >> -- >> Fabien Potencier >> Sensio CEO - symfony lead developer >> sensiolabs.com | symfony-project.com | aide-de-camp.org >> Tél: +33 1 40 99 80 80 >> >> Kris Wallsmith wrote: >>> One complaint I get from a lot of developers new to symfony is >>> "why do >>> I have to clear my cache when I'm in the dev environment?" I'm not >>> sure I have a good answer! >> >>> Why do we use the cache in development? Shouldn't I be able to >>> pass a >>> sfNoCache object into the sfConfigCache and eliminate even the >>> autoload and config caching? >> >>> Would anyone else like to see an upgrade along these lines in a >>> coming >>> 1.x release? >> >>> Kris > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
