On Sat, Dec 27, 2008 at 4:53 PM, Tycon <[email protected]> wrote:
>
> The webhelpers.pylonslib.Flash class is kind of poor. It's a bad idea
> to flash
> a message about a previous operation after redirecting to an unrelated
> page.

Yes, very opinionated.  Why don't you join the
sessions-and-cookies-are-evil club while you're at it.  If the page
layout has a space reserved specifically for status messages, there's
nothing wrong with using it.

> It's just as bad to use the session as temp storage for such things
> (incurs filesystem/db
> access if you use multi-process design to serve the app, unless you
> use memcached
> but that doesnt work in beaker right now).

This assumes that most applications want to use a multi-process
design, or that they are so high-traffic the disk/database access is
intolerable.  Only a minority of applications are like that, and those
that are have several ways to optimize, of which this is only one.

> It's best to use the c global and display an acknoledge page with the
> flash message(s)
> and let the user redirect using link(s) on this page.

That gets into usability.  Is the message important enough to
interrupt the user's work and force them to click again and wait for
the page to load a second time?  I have found two main uses for flash
messages.  One is confirmation that the expected action did take
place; the other is for error messages.  Putting up a flash message
ensures the user notices it without interrupting their work (i.e.,
without delaying the page they wanted to see).  And the message is not
so drop-dead important that the sky will fall if the user doesn't
notice it.

-- 
Mike Orr <[email protected]>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to