|
Michael Jouravlev wrote: For this particular case it is fine. But not for every case.On 8/3/05, Matej Knopp <[EMAIL PROTECTED]> wrote:Btw. What do you think would be correct action? If i have heavy pages the the backbutton should be quick that is the whole idea. And besides that.you can always have stale data at anytime. Because Matej is still going to need to build in the check on save of the assigment if it is there he done that now because of opera, but he should also do it because of every browser Because if i open the assigment it is still there. The i press save but you on the other side of the world did already a delete of it. Then my save should be handled gracefully, and display the message to me that it was already been delete (maybe telling me who did that) So saying that a reload on back fixes everything is just wrong. a browser can have stale data at any time if you work in a multi user environment (what a webapp mostly is :)) But i agree that it is for this a nice add on. then you get warned at font. Maybe we could build it in that you can set it on easy for specific pages.. johan |
- Re: [Wicket-user] My wicket application Michael Jouravlev
- Re: [Wicket-user] My wicket application Matej Knopp
- Re: [Wicket-user] My wicket application Johan Compagner
