Hello, Does anyone else have a problem with Ajax.Updater where you have some links "x, y and z" which call Updater to load content into your target container on the page somewhere..
Click "x".. that's fine... then maybe click "y".. etc. But, if the user's connection or the server's a bit slow and they click "y" before the "x" has finished loading the page kinda flickers.. and the user experience is a little spoiled because the page starts to not keep up with the user's interaction... I've made a little change to our version of prototype ( half a dozen lines or so ) which, if you give the parameter "override:true" to Ajax.Updater() it will record the stack of requests going to each target. That way, if there are two or more concurrent requests who's content will eventually end up in the same place only the last one gets executed. What this _doesn't_ do is actually cancel the requests.. ( I don't know how best to do that! ) it simply makes sure that only the last request in the stack get's inserted into the target ( and at the moment only the last request's javascript gets eval()'ed ) . Anyhow - just wondering if this sort of thing is worthwhile enough to comit back into the cvs?? Would anyone find this useful, is it the right sort of thing to commit? Thanks, Jimbo. PS. Since this is my first post to this list: Thanks Sam, et al! Great library! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
