Hi both 2) and 3) look easily doable to me, personally I'd prefer a ttl of the user information as in 3) We *might* also find a smarter way to decide when the user needs to be reloaded, e.g. when the user data has changed substantially. I do not know enough of the frontend logic atm however to really suggest how this could be done in detail.
Stefan On Jun 6, 2011, at 3:33 PM, Lukas Kahwe Smith wrote: > Hi, > > Many months we made the decision to always call refreshUser() on every > request. Now this makes sense as a default and obviously when using some > expensive data source one should consider some sort of caching for this. > However I think we should provide some simple ways to reduce the number of > calls to the data source, basically I think we should cover the following > scenarios > > 1) fetch on every request > this is what we have today > 2) fetch every X requests > 3) fetch after Y amount of seconds > > For both X and Y we should probably also include some ways to easily set the > interval dynamically on the first load and subsequent refreshes. > > This will imho cover the bulk of what users will need in practice without > having to make the user implement similar logic in every user provider. > > Gruss, > Lukas -- 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 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
