On Dec 1, 11:02 pm, Lee Bolding <l...@leesbian.net> wrote: > Whilst I'm still not convinced it's the "best" approach (but one that I'm > currently using... for now), you could fire an event from your model, which > an observer would use to clear the cache. > > This is a little cleaner as it loosely couples the model to the caching > implementation, and means your event and observer are reusable. It also means > that your model is reusable in a scenario where you don't want this behaviour > (for instance, when used with webservices)
This indeed seems to be the best way that is currently possible with Symfony. Where do you do the actually removing of the cache? Cheers, Tijmen -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
