I like the idea of modularity, which would be more practical for your environment. I have written an article on how Ajax.Request could be modified to accommodate for a timeout event. Feel free to read the article / source code. I wouldn't really recommend it for your "live site" but its perhaps worth looking into for curiosity's sake.
http://positionabsolute.net/blog/2008/07/prototype-ajax-request-timeout.php On Dec 15, 7:16 am, lorry <[email protected]> wrote: > On a live web site, I'm experiencing a small number of cases where > Ajax.Updater requests are not completing, leaving the user with an > animated "loading" icon. On investigation, it appears that this _may_ > be related to firewall configurations and in other cases "ad blocker" > applications. > > We can't control the customer's environment, so we already degrade > gracefully where the user's browser has javascript disabled, however I > am trying to work out how to "degrade" back to simpler UI > functionality where ajax requests using protocol fail to complete. > > My first idea is to re-code so that there is a timeout of say 15 > seconds, then tell the user that the request is taking a long time and > suggest that they switch to a basic UI & save that preference in a > session cookie. The code is all modular, so I can essentially drop > the user back into the same UI as if they had javascript disabled. > > What do you think - is there a more elegant way of doing this or? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" 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/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
