Linked by Thom Holwerda on Tue 27th Sep 2005 22:34 UTC
General Development Strong error handling translates into more reliable applications. When you load an XML document, it is best to catch errors early, before they have a chance to damage other data. I have noticed that many companies and developers make the same mistakes when they adopt XML technology. Learn how to avoid common XML coding errors when you design and implement error handling in XML applications.
Permalink for comment 37313
To read all comments associated with this story, please click here.
RE: The best XML practice...
by Clinton on Wed 28th Sep 2005 06:16 UTC in reply to "The best XML practice..."
Member since:

I agree with you for the most part. I think XML has a place, but its place is very small.

Probably 95% of the projects I've been forced to use XML on could have been done much more efficiently some other way.

The problem is that people making decisions often make them based on market hype. To give an example, when I worked at Novell, one of the managers went to an XML conference and came back and informed the team that we were going to do all future development in XML. He asked one guy to research and find the best XML IDE out there.

This is extreme, but I think a lot of project suffer from XML due to this same level of insight.

Reply Parent Score: 1