Now that I am back home, I just tried this and the answer is no, it does not. It does replace an element with the same id if you send it again so you do see live changes as you describe. However if I drill down several layers in my app then go back up and look at the dom in web explorer then the complete dom is still there with all the elements from where ever I drilled down to.
Fortunately for me, my backend keeps track of the logical level that the client is at by embedding a level parm into each link. It does that so that it can generate unique ids for the results divs it returns. By capturing the aftertransition event I can run a script to delete everything from the dom with a level number higher than whatever the level of the target page is. I am planning on caching the static stuff (css and scripts) via a manifest once development is complete (or as complete as it's going to be). My content is highly volatile and pretty much impossible to cache although I am considering using a client side database to implement a 'more' function. Send all the data but only display say the first ten rows, get the next ten from the internal db until user drills down to next level up up to previous level. Can't do 'more' from the server because of data volatility. And to think I am doing this for 'fun!' Thanks for you input, Dave E -- You received this message because you are subscribed to the Google Groups "iPhoneWebDev" 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/iphonewebdev?hl=en.
