On 13.09.2010 17:21, Fabien Potencier wrote: > On 9/13/10 5:16 PM, Tom Boutell wrote: >> Philosophically I think this is a great solution. I hope the >> performance issues can be finessed. My understanding is that templates >> are a lot faster in 2.0... > > I have not done any serious benchmark. It is just a feeling I have. And > yes, templates are much faster in Symfony2.
If we do this, you really have to be careful about performance. PHP templates must have very little overhead compared to a straight include statement for it to work. I know a guy that built a framework where every template was composed of sub-templates in a similar manner, and using Smarty (which is not as slow as most people like to think) he ended up with something that didn't perform very well when too many forms etc were present. As a reminder, another possible approach is the way Agavi does it: you just define your html by hand (it could be optioanlly rendered by those subtemplates and cached) and then validation/auto-fill is added by transforming the output of the page with xslt. The advantage in this case is that you only call the slow code when the user actually submits a form and it doesn't validate. All other requests are just hitting the template and rendering straight. Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- 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
