What you can do instead, Michael, is make going back going forward. Do you have a do/undo/redo app in your programming toolkit?
Jack On 4/28/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > On 4/28/05, Rick Reumann <[EMAIL PROTECTED]> wrote: > > Michael Jouravlev wrote the following on 4/28/2005 11:35 AM: > > > > > What I meant is that if you always resubmit, then you cannot refresh a > > > form without resubmitting again. > > > > I'm not sure what you mean here. If you plan to reshow the same form > > again after you submit you could either A) if you using Request scope > > just stick the form back into scope in your Actoin or B) if using > > Session scope, do nothing. Neither require the use of hidden vars. > > This is just an old issue of mine. I do not like to show page > immediately after posting data simply because this page cannot be > refreshed properly from a browser. This is why I prefer to use session > scope to save data after I redirect to show the page. This issue does > not directly relate to original "show old values" issue of this > thread. > > > > What if you DO need to go back and to resubmit? > > > > Well I'm confused. If you want to allow the to rebsubmit then don't use > > the Token. If you want to ensure they do not use duplicate submits then > > you implement the token. I must be missing something because I don't see > > how the use of hidden vars and, even worse, 'oldValue', 'newValue' > > hidden vars makes things any easier? > > > > Can you explain a situation that requires their use as was defined in > > this thread? (Don't get me wrong, I see the use of hidden vars, but > > never to represent my whole form's previously submitted values.) > > You are right, they do not make things easier. I was not arguing with > you. I don't know why I decided to reply on this thread. I just think > that (a) storing view state in hidden variables is not the best > solution, and (b) using token is not the best solution either, because > it is provided by web layer, which knows nothing about underlying > domain model. I prefer to rely on domain model in this case. I also > hate "Do you want to resend POSTDATA?" message with all my guts, but > seems that I am in the minority here ;) > > Imagine a website which sells some car parts. You select your make -> > next page, model -> next page, category -> next page, part > manufacturers -> next page, you found the list of parts. No, wrong > part. Probably wrong category. Or you want to check other car model. > You click back -> back -> back to return, and _each time_ browser > first asks you: do you freaking want to resend postdata? Yes! It > reloads the previous page by submitting the same request, it also > takes time to prepare the _same damn query_, of course. What if you > answer "no"? Then it either stays on the same page (Mozilla), or shows > "page expired" message on blank screen, if it is MSIE. Imagane > yourself a regular user, would you know what a POSTDATA is??? I would > kill the guy who created this interface. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
