Thank your for your answer Francois, but i think my question was not clear enough :
I think it would be interesting to cache the add javascript and css building process even if you don't turn on layout cache. In many cases, the whole page do not use layout cache feature, or at least just cache some part of the template or some costly processes. However, caching this process should be hard to implement, since you can add javascripts dynamically in your code :/ I will take a look at dustin's question about environnement handling in view config files for my specifics needs. Thank you for your patience, and again, thx for all your work :p On 6 avr, 11:38, "Francois Zaninotto" <[EMAIL PROTECTED] project.com> wrote: > Hi David, > > As indicated in the symfony book, the cache filter executes before the > common filter. If a page is found in cache, the cache filter bypasses the > other filters and goes (almost) directly back to the rendering filter. So > when a page is found in cache, the common filter isn't executed at all. > > François > > 2008/4/6, david.stendardi <[EMAIL PROTECTED]>: > > > Hi all ! > > > Would like to know if there is a particular reason why sfCommonFilter > > do not use cache feature to avoid repeated calls to get_javascripts && > > get_stylesheets. I think this would speed up a bit response since > > these calls are made on each request. If there is no particular > > reason i will work on patch and proposed it attached on a trac > > ticket. > > > Thank you ! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
