gps wrote: > Adding the specific path to the cookie fixed the firefox flash message > presists forever problem. thanks! > > Glad to see I'm not the only one who thinks a cookie is a bad way to > store a critical message for future display. nothing guarantees a > browser or intervening proxy will even accept cookies.
As more people are reading the ML, I cross-post what a wrote here: http://trac.turbogears.org/turbogears/ticket/32 How about using cherrypy.session for this? I suppose we don't get around using cookies in one or the other form if we don't want to use ?SESSIONID=<uglyhash>. We could insert this in dev.cfg: # If you want to use tg_flash() you _must_ uncomment this. # Warning: Your app will require a cookie-enabled browser then! # But as a benefit you get a global session via # cherrypy.session (a dict) for free :) #sessionFilter.on = True #sessionFilter.cookieName = <appname>SID Then tg_flash() could simply set/unset cherrypy.session['tg_flash_msg']. Fabian
