Be aware - the preferences API on Windows will want to store settings in the Registry which may make uninstall a harder problem ( the application will no longer be in just one parent root directory ). ------------------------- JCertify 6.0 now available http://www.enterprisedeveloper.com/jcertify The best investment in your career you will make all year
--- Joseph Ottinger <[EMAIL PROTECTED]> wrote: > Your reasoning's correct, and I'd suggest that human > readability is by far > more important in the long run, so mention it a few > more times. You might > also want to consider property files instead of XML, > as you get the same > benefits as XML except you don't have to muck about > with Digester or some > custom reader, and they're also faster to work with. > Use XML only when your > data structures are complex enough to require it, or > when you're sending > your data across architectures or applications. > Using XML internally for an > application impresses the heck out of the geeks, I > guess, until they have to > do it themselves and then they wonder why all the > man-hours have been poured > into the technology... > > (I use XML myself for a number of things, including > configurations in a few > apps. :) > > > >From: "Ivan Bradac" <[EMAIL PROTECTED]> > >Reply-To: "JDJList" <[EMAIL PROTECTED]> > >To: "JDJList" <[EMAIL PROTECTED]> > >Subject: [jdjlist] Serialization x XMLization > >Date: Mon, 2 Sep 2002 09:03:33 +0200 > > > >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 > > > ----------------------------------------------- > Joseph B. Ottinger [EMAIL PROTECTED] > http://enigmastation.com IT Consultant > > _________________________________________________________________ > Chat with friends online, try MSN Messenger: > http://messenger.msn.com > > > To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm
