Storing application state as XML

[David]

> From: Steve Kearon <stevek at fineline-software.co.uk>



> When opening a file, we tolerate quite a lot (eg someone could add
> attributes/elements that we'll ignore).

	Various issues can arise when you modify
a class, then try to deserialize objects stored by the 
earlier version. So the decision to ignore unknown attributes 
can become important later on. Have a look at Java Serialisation 
and see how they address it.


				David Byrden
				http://byrden.com/rubxml



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)