Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Add Persistence to Your XML Data Islands-3 : Page 3




Building the Right Environment to Support AI, Machine Learning and Deep Learning

Updating Records
Updating records is easy because you don't need any scripting whatsoever. IE hides all the plumbing involved in using the data island component, it is responsible for keeping the display coordinated with the data. For users, this automatic synchronization makes updating records a snap--just type a new value into any bound data field in the associated form and move off the record. That's it! The bound form field's new data replaces the data in the XML document.Of course, it couldn't be that easy! As you found out in last month's article, at this point, the XML data exists only in memory—not in a persistent store. Therefore, even though users can see their changes to the data by navigating through the record set, reloading the page reveals that nothing has really changed; the data island still contains the original data from the phone.xml file specified by the src attribute of the <xml> element. Because the underlying file remains unchanged, the page always displays the original data. From a developer viewpoint, IE's automatic synchronization between the display and the in-memory copy of the data is not the same as automatic persistance. When you need persistance, you must implement it yourself.

Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date