For a desk top application I would definitely go with XMLisation. It really needs to be human readable so that errors that might prevent the app from starting can be corrected by hand. Also, as you said, it's an easy way to avoid serialisation issues, to keep future compatibility in mind, and even to change the language that the app is written in should that ever be necessary. You can get fairly good libraries which will help enormously with this.
 
regs
scot.
-----Original Message-----
From: Ivan Bradac [mailto:[EMAIL PROTECTED]]
Sent: Monday, 2 September 2002 17:04
To: JDJList
Subject: [jdjlist] Serialization x XMLization

Hi all
 
We are developing a desktop application. It is necessary to set up  a system of storing the user's workspace settings. I think there are two standard options how to do this:
 
1. Serialization
2 . Store the settings in an XML file or a set of XML files.
 
I wonder which of theses approaches suites better. As of now, I can think of the following pros and cons :
 
Serialization:
pros: easy to implement, it is built in java, java objects directly are stored
cons: the stored streams are not human readable, there may be problems with versions of the serialized classes. Only a java application can read this data. 
 
XML filesystems:
pros: Human readable and editable, a standard way of storing data, not dependent on the programming language
cons: requires more work at the implementation, at least at the beginning
 
Right now I am more in favor od the XML filesystems solution. Does anybody have any opinion ar experience with this topic?
 
Thanks
 
Ivan
To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm
To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm

Reply via email to