On 06.06.2011, at 15:43, Stefan Paschke wrote: > 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.
well we can also think of a 4) where basically we have a listener that defines if to refresh the user or not. this would allow a backend to notify the frontend that the user should be reloaded if its for example older than version X because there have been changes to that user (like their subscription changed etc). regards, Lukas Kahwe Smith m...@pooteeweet.org -- 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
