I believe you can make the cache key whatever you want... so in your case just module/action and whatever neccessary parameter, but not user id. I've used this in reverse, where I had the same url for everybody, but depending on the login status and session id I'd generate a unique cache key, since the content chanced per user.
Daniel On Jan 21, 5:44 am, Gabriel Petchesi <[email protected]> wrote: > Symfony builds up the cache key based upon the URL in case of action or > parameters (for partials, components). > > I'm not sure if you can override the cache key within the action so my > suggestion is to create a simple action with a template and within > that template include a component that will be cached. > > For that component set up the cache_key value however you want, it could be > any of the following: > include_component('service', 'provider', array('sf_cache_key' => > md5($service.$ver.$lang))) > or a concatenated string with the important values > include_component('service', 'provider', array('sf_cache_key' => > $service.$ver.$lang))) > or by specifying exactly the elements you want to be used for caching, > symfony caching will compute a hash based on that: > include_component('service', 'provider', array('service' => $service, 'ver' > => $ver, 'lang' => $lang)); > > For improved speed you could look into something like the sfSuperCache to > avoid loading the framework altogether, not sure if it works > for Symfony 1.4. > > gabriel -- 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 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
