Hi, I saw the conference earlier and Fabien said there was no way to invalidate an item in the cache in Symfony2.0.
I asked a question about whether the cache could be invalidated in response to user action such as adding a friend on facebook, and Fabien replied that that functionality would need to use the 'validation' cache method. Isn't this going to be inefficient for data that rarely changes, but which when it does change should be updated in the cache immediately? This isn't such an edge case -- all the sites I work on have content that falls into this category to some degree, for instance content on a web site which can be cached indefinitely, but should be refreshed only when an admin edits the content. In the case of content, obviously a TTL of an hour or so could be used, but if this dynamic data was associated with a user object, revalidating with the cache at intervals could add unnecessary extra load. I think it's important to support this kind of behaviour. Admittedly we haven't deployed an HTTP accelerator so I'm not 100% clear on what action it would have to take to revalidate an object, but it's bound to add unnecessary load and inefficiency to the application in this case. What are your thoughts? And if you're definitely not going to support object invalidation, would it be possible to provide a workaround? Thanks -- 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
