Configuration is generally pretty static and XML just provides a better
way of adding structure.  However, performance can be very good. It all
depends on your priorities. A couple of lines of Java code with JDOM can
build a configuration object that runs anywhere with little change
because it can rely on APIS that are part of any 1.4+ JDK. If
performance is a priority, I might opt for a configuration object that
implements a SAX interface, for example to configure how an individual
email is sent. This last case wouldn't be as simple and requires setting
environment variables to identify the SAX implementation.

David Morris

>>> ALBartell@xxxxxxxxxxxxxx 9/13/2004 9:06:54 AM >>>
Storing config info in XML for Java is peaking my interest here.  I
been using xml config files for other packages for some time (i.e.
Tomcat) but haven't built it into any of my home grown programming. 
these performance efficient enough being that you have to parse the
data?  How often do you parse the config?  Once per HTTPSession/AS400

Aaron Bartell 

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.