Hello,

I'm here to ask the age old question...  I know there are many answers too it; but adding DNN to the mix causes me to ask it again; I could dig in my toolbox for one of the dozen ways I've solved it in the past, however sometimes it's better to learn quickly from mistakes others have already made.

How can I disable user navigation while a long postback is taking place?  Not only in the module i'm writing - but in all other modules and most importantly the menu.  The best example of "Why" is to prevent users from causing a double postback durring credit card validation.  I understand that this can be prevented at the server...  But I have other reasons why I don't want a user to stop waiting and click on a menu item before they get to the page they're trying to load.

Has anybody experimented with a generic client side java routine that will disable all postback objects in all modules including items on the page because of skin tokens (such as the menu). or placing a clear DIV on top of the menu items to prevent them from being clicked?

I understand that whatever solution I come up with is going to be a "hit and miss" solution...  that someone can always hit the back button, or navigate to a previously saved link or website altogether.  My needs do not depend on the using getting to the page they are waiting for...  but if I could spend a little bit of time to solve the problem for 85% of scenarios / users... then it could be worth it.

Matt Christenson

www.RealSkydiving.com

I am familiar with using Ajax but only for a few third party controls from Infragistics and some home built controls.  I have not used it very extensively because at the time when I put the most research into it (about a year ago) it still did not have a powerful framework associated with it and browser compatability made me concerned.

The first option that you suggested is what I had planned to do if I was not able to come up with any way to disable the entire page (menu system)...

I am not familiar with an Ajax update panel.  Are you referring to a part of Atlas?  This is something that I have been waiting for a good time to get involved with; I am concerned that the learning curve may be large enough to de-rail my ongoing development efforts; and that browser compatability and stability issues on the server side could leave me with a problem that I am unable to solve myself.  It sounds like you've used them.  What do you feel about their overall usefulness and stability across a wide variety of internet browsers?

Thanks,

Matt