On Jun 3, 2013, at 8:52 , Fabien Potencier <fabien.potenc...@gmail.com> wrote:
> So, if Symfony 2.4 was just about 1 new major change, which one would it be > for you? Another topic would be improvements for caching. The ezPublish guys have implemented a solution to track node id's and add them as a custom header which can then be used by a reverse proxy to do purges based on node ids. This goes slightly in the direction of https://github.com/rails/cache_digests. I think SonataCacheBundle also has something like this. I think it would be great if we could add some infrastructure to make this sort of thing easier along with implementing this for example also for Twig templates (ie. being able to deploy a new version of the code and then running a command to automatically purge everything from the reverse proxy for which the template changed). To make this work with HttpCache we would then also need to expand the metadata we keep for cache entries, which in turn again likely means integration of a proper cache library that supports tagging. See also https://github.com/symfony/symfony/pull/6213 regards, Lukas Kahwe Smith sm...@pooteeweet.org -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
