Hi Debbie, At that point we're really just into application logic. Keep your displayed list of tickets then ideally have ticketdata return only changes (e.g., "give me modified tickets since X" where X is the date/ time of your previous request), which you then apply, or in the worst case you compare the data for your currently-displayed tickets vs. the latest from the server and apply any changes to the display.
Good luck with it, -- T.J. Crowder tj / crowder software / com On May 23, 4:36 pm, Debbie <[EMAIL PROTECTED]> wrote: > Thank you very much, T.J. I'm very interested in being able to > process only the changes in the ticket list. Suppose I can transform > responseText to JSON array of tickets, can you show me how to keep > track of the previous and current JSON array, identify the row that's > changed, and update only the changed content in the tr? > Thanks, > Debbie > > > Of course, rather than tearing everything down and rebuilding it on > > every refresh, your code would want to process only the *changes* in > > the ticket list; note that I've marked each row displaying a ticket > > with an ID derived from the ticket ID, so you can easily grab just > > that row and update its contents if the ticket details change. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
