> Also, after the user drags an item we make an Ajax call to update the > sort order and persist it. The Ajax call returns the HTML to replace > the entire list/groups of items. When there is about a 100 items the > display is not refreshed correctly. It seems that perhaps the Ajax > returned HTML might be replacing a portion of the DOM that > Script.aculos.us/prototype is still processing. > > Any suggestions on how to improve performance?
I was having a similar problem in an application currently (STILL!!, my customer would add :-) under development. In the end I resorted to having the Ajax call return mere data (an array of Javascript objects representing items in a list) and generating HTML client-side, using Prototype's Template class. Yuor case, however, may be simpler since, if I understand correctly, once the user has dragged an item you already have the ordered list on your page; thus the Ajax call does not need, IMHO, to return anything if not "OK" or something of the kind, and you would just have to handle the occasional failure, e.g. by simply reissuing the call. Ric --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
