True, until I have multiple elements that should NOT appear in the URL (like sensitive keys, status messages, etc) and which were nicely obfuscated by M2's persistID. I guess it looks like it makes more sense to use my own persistence system and do as you are saying, expose that ID in the URL.
-Brian On Jan 24, 1:01 pm, "Peter J. Farrell" <[email protected]> wrote: > Brian H. said the following on 01/24/2012 11:56 AM:> Really. Has this always > been the case? Any particularly justification > > as to why? > > Yes, it has always acted in this way. Redirect persist is basically a > "flash" scope to fix the issue of not being able to do a redirect and > loosing the current request. Basically redirect persist is basically a > "faux" way to make two requests (initial one and the redirect) into > "one" request. > > > This is worrying to me as I build my applications so that > > non-action pages (listing screens, managers, etc) can be refreshed > > without causing a problem. With these variables deleted after first > > request, that is no longer possible. > > > Normally I've only persisted things such as response codes to show the > > user a message, so refreshing would cause the message to disappear, > > which wasn't a bit deal. However now I am persisting a special key > > through my redirections, and the process would be broken if the user > > ever refreshed. > > Put that key in the URL. Use the "args" attribute of <redirect> or the > args argument of RedirectEvent() to stick an additional key in the URL. > > .pjf > > -- > Peter J. Farrell > [email protected] > [email protected]http://blog.maestropublishing.com > Identi.ca / Twitter: @maestrofjp -- To post to this group, send email to [email protected] For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
