On Sat, Jul 28, 2007 at 11:21:56PM +0200, A. Pagaltzis wrote: > > User visits page A. > > User visits page B in another tab. > > User submits form A. > > User submits form B. > > A updates the flash. > > B updates the flash. > > Page A2 loads with whatever flash won. > > Page B2 loads with whatever flash won. > > Keeping implicit state on the server blows. News at 11. > > (The right way: don’t use flash. Put the stuff somewhere > where you can give it a URI and send the user to that > address.)
So simple case: client posts which updates a user "Foo". You redirect after post and want to display 'User "Foo" was updated' (or something you need to store server-side between the post and the redirect). What's your approach? Always pass around a session id in the URL? On redirects pass an unique id to get at that request-specific message? If so, how do you manage orphans, say if the redirect never happens? -- Bill Moseley [EMAIL PROTECTED] _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/