On 7/13/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > See this thread for insight: > http://forums.mozillazine.org/viewtopic.php?t=99885&start=0 > I understand that by posting this link I can swing the scales to "do > not reload" decision, but again, I want to have an option for myself, > I do not suggest to make all Wicket applications reloadable.
I just reread what this guy posted. So, he is a "power user", he wants to to go back and see page as it was. He also wants browser to have a setting to override cache control headers. I can see his reasons. On the other hand, he says, that when he goes back, he wants to see page from cache. But what if we don't give him a chance to go back? ;) A web island has no option of going back, so this guy would have nothing to bitch about. Still, his examples is based on reading email. Email is more static thing than say a wizard or a stock exchange front end ;) Also look at Google Mail. Times change, things change. Ajax does not leave much for going back ;-) Michael. ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
