Parse all the directories, on every request(!), to check if a new class was added?! Look how often users complain about symfonys performance in dev mode. It's very easy: every time you add a new class, you call cc. This is for sure a bit overhead in the beginning of a project. but once everything is build and you only tweak your code, then you'll be happy that symfony response is "fast".
I don't mind to type cc. Michael On Sep 29, 7:26 pm, "Tom Boutell" <[EMAIL PROTECTED]> wrote: > If the cache back end for the config cache can't be overridden with > another, then it should be patched to allow its current "throw out the > umask and make everything world writable" behavior configurable. The > current code has to be manually patched to be suitable for use in a > shared hosting environment: > > http://trac.symfony-project.org/ticket/4412 > > On Sat, Sep 27, 2008 at 1:38 AM, Fabien Potencier > > <[EMAIL PROTECTED]> wrote: > > > It does not make sense as the configuration files are included and in > > PHP, you can only include a file... and I don't want to use eval() ;) > > > Fabien --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
