Hey guys- Requiring the proxies and hydrators to be generated really kicked my arse last night... and I'm *kinda* smart. I don't think requiring this of all users is realistic, and I think it'll cause a lot of heartache either during development (when they finally switch into the prod environment) or after they deploy. I realize you can change this setting, but user's will only discover this AFTER they've deployed to prod or hit their head against their desk for hours :)
I realize the problem with generating on every request in production, but isn't there a middleground? What about the following (by default): * always generate these classes in dev * generate conditionally using a file_exists() in prod * Keep the option to never generate proxies or hydrators for advanced users (but it has to be explicitly enabled). Requiring these classes to be generated effectively means that you need to have an automated deployment. That's best practice but just not a reality. Bulat proposed that there could be a check.php or CLI task that checks your app for "production" settings and warns you when things are non-ideal. Perhaps that could be rolled into whatever deployment tools we eventually craft and perfect. Thoughts? Ryan Weaver Lead Programmer - iostudio - Nashville, TN http://www.iostudio.com http://www.thatsquality.com Twitter: @weaverryan -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
