Hi, First time here but I have some comments that I thought would be worth sharing with the dev team. Recently upgraded a large 1.0 project to 1.3, found it running very slowly in some modules, tracked this down to the autoload cache being reloaded on each request.
I found a mention that this was an experimental feature. Love the concept but I have a use case that prevents the use of sfAutoloadAgain: Should I require to know if a class_exists, and due to the logic of the app its perfectly reasonable that this class may not exist nor even be defined, then it will fire the spl_autoload chain not find the class and cause the autoloader to reload. I heavily use the DbFinder plugin and this plugin uses class_exists for in this exact way. I'm not sure whether you would consider this an edge use case or not. Whilst I'm here, thanks for building such an awesome framework! Mark -- 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.
