On 11.03.2011, at 20:41, Fabien Potencier wrote: > The semantic of the flash feature is that flashes are persisted only for the > very next request. This behavior cannot be changed because all other > frameworks (including symfony1) have this very same behavior. > > I will work on a patch or merge the PR.
i guess there isnt enough reason to stray from "established standards" here. however i would like to raise another point: it seems to be like flash messages do not go well together with ESI i guess one solution would be to register a core.reponse listener and place the (translated) flash messages into a cookie that the reverse proxy is configured to ignore. since the translation part is hard to do generically (unless we make a configurable catalog), its hard to provide an out of the box solution for this. so probably worth a cookbook entry? regards, Lukas Kahwe Smith [email protected] -- 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
