I have found something in the book that is the key I'm searching for: You need to add your filter to the filter chain, and for that, you must declare the filter class in the filters.yml, located in the application OR IN THE MODULE config/ directory, as shown in Listing 6-32.
Notice the "in the module". So, I can create my own filter just for that module. That is what I was searching for. Thanks anyway :) On Apr 27, 11:51 am, HiDDeN <[email protected]> wrote: > Ok. But there is another problem: I use memcache as my cache. Will > this be a problem? > > On Apr 27, 11:40 am, Thomas Rabaix <[email protected]> wrote: > > > It should be compatible; there is no much changes in filter/cache between > > 1.1 and 1.2. > > > On Mon, Apr 27, 2009 at 11:32 AM, HiDDeN <[email protected]> wrote: > > > > Thomas, I use Symfony 1.1, and I see that your cache filter is > > > compatible only for 1.2 version > > > > Is there some other solution, please? > > > > On Apr 24, 6:50 pm, Thomas Rabaix <[email protected]> wrote: > > > > just use swUserContextCacheFilter.class.php< > > >http://trac.symfony-project.org/browser/plugins/swToolboxPlugin/sf1.2.. > > > .>class > > > > as your cache filter ;) > > > > > If your main action is name 'view', just create a > > > > executeView_UserContext > > > > action. This method will be always called. So you can perform user > > > specific > > > > code in that action. > > > > >http://trac.symfony-project.org/browser/plugins/swToolboxPlugin/sf1.2... > > > > > On Fri, Apr 24, 2009 at 6:18 PM, HiDDeN <[email protected]> > > > wrote: > > > > > > Yes, I know that. I did read the book. But that action makes heavy > > > > > queries to the database, so, if I just cache the listing of the data > > > > > I'm getting, I will be executing always those heavy queries... that is > > > > > the reason I was caching the action. > > > > > > On Apr 24, 5:13 pm, Eno <[email protected]> wrote: > > > > > > On Fri, 24 Apr 2009, HiDDeN wrote: > > > > > > > Eno, what you are recommending is to cache parts of the template. > > > > > > > I > > > > > > > need to cache the action as well. > > > > > > > But you need the action to run as well. You can't have it both ways > > > > > > - > > > > > > either you run the action or you dont. The only way you can get the > > > > > action > > > > > > to run every time is to NOT cache it; intead you cache partials and > > > > > > fragments of the template. > > > > > > > Seehttp:// > > > > >www.symfony-project.org/book/1_2/12-Caching#chapter_12_sub_cac... > > > > > > where it says: > > > > > > > "Action caching applies to only a subset of actions. For the other > > > > > > actions--those that update data or display session-dependent > > > information > > > > > > in the template--there is still room for cache improvement but in a > > > > > > different way. Symfony provides a third cache type, which is > > > dedicated to > > > > > > template fragments and enabled directly inside the template. In this > > > > > mode, > > > > > > the action is always executed, and the template is split into > > > executed > > > > > > fragments and fragments in the cache, ..." > > > > > > > -- > > > > > -- > > > > Thomas Rabaixhttp://rabaix.net > > > -- > > Thomas Rabaixhttp://rabaix.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
