The typical solution to that is to return from the POST with a redirect header, forcing the client to issue a GET thereby placing a new most-recent history entry. It is surprising how few e-commerce sites honor this idiom though, double-submit remains a real issue in 2010.
On Nov 6, 10:12 am, Fabrizio Giudici <[email protected]> wrote: > On 11/06/2010 06:03 AM, Cédric Beust ♔ wrote: > > > With a Back button, the cognitive dissonance would actually be much > > lower. It's the perfect illustration of"Don't make me think" > > <http://www.amazon.com/Think-Common-Sense-Approach-Usability/dp/078972...>. > > Partially agree and partially not. I mean, there are actually a lot of > places where back makes sense. I'm extensively using it e.g. in my > Android application. But there are cases in which it starts not making > sense, for instance when you perform non reversible operation. The "pay" > page is a typical example. Note that since nobody can block the back > function in a web browser, everybody providing a pay service is forced > to print in flashing colors "DO NOT PUSH BACK UNTIL THE OPERATION IS > COMPLETE". So, while it makes sense to provide back functions, it also > makes sense to disable them at least in some places. > > -- > Fabrizio Giudici - Java Architect, Project Manager > Tidalwave s.a.s. - "We make Java work. Everywhere." > java.net/blog/fabriziogiudici -www.tidalwave.it/people > [email protected] -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
