[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Principles of XML design

• To: Chris Burdess <dog@b...>
• Subject: Re: Principles of XML design
• From: Peter Hunsberger <peter.hunsberger@g...>
• Date: Fri, 6 May 2005 16:48:32 -0500
• Cc: XML List Developers <xml-dev@l...>
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YDJ1S1ECICYjQ65aOTSnLzeuejscPCbKFJphsWAhb8Lf8lv5JEwQYr7LsFiGptrRidR5Tu5kRNmfozrly5Beq1PwwIoUCAyfyJsxQ5Um+MZVPvPPbgqfwfZ0yk6ql/AdVn+k3Xq24U5gJw52sQ3kR7eVkyOTAADSgrMrJ2UUZyM=
• In-reply-to: <20050506213052.GB7407@b...>
• References: <20050506170322.498F52A46A2@m...> <0fa13582277ef91a61197ef274c686b8@r...> <be524b26c07df26e1469df591cd17742@b...> <cc159a4a050506140815e72d26@m...> <20050506213052.GB7407@b...>
• Reply-to: Peter Hunsberger <peter.hunsberger@g...>

On 5/6/05, Chris Burdess <dog@b...> wrote:
> Peter Hunsberger wrote:
> > Just out of interest: when are "users" going to be switching between
> > parsers for a given application?  Even as a developer once I've picked
> > a particular parser for a particular application I've pretty well
> > committed to it for the lifetime of the app...
> 
> In Java, the standard means of retrieving a parser implementation (JAXP)
> is user-overrideable. The user can choose a different parser by
> specifying different system properties. They may decide to run your Java
> application on a different platform, one for which the default parser is
> different. They may do this to experiment with different configurations
> and performance and stability, or for instrumentation, or they may be
> completely unaware of it, the decision to use another implementation
> having been made by someone else (following an operating system upgrade,
> etc).
> 
> If you're used to developing in C with libxml2, this may sound arcane.
> But even within such a static codebase, software changes: new project
> managers and system architects come and go, and refactor the "legacy"
> code according to their own experience and understanding of the domain,
> including the XML specification.

I develop with Java, I'm well aware of JAXP and its kin. They're nice
in theory, but for any moderate sized application, even with "100%
conforming" parsers (whatever that might mean), any developer who
leaves it to chance as to what parser is picked at any given moment is
just asking for trouble; if you're not careful you might fall back to
the default Xalan parser (bugs and all ;-)

-- 
Peter Hunsberger

• References:
  • Re: Principles of XML design
    • From: richard@i... (Richard Tobin)
  • Re: Principles of XML design
    • From: Gavin Thomas Nicol <gtn@r...>
  • Re: Principles of XML design
    • From: Chris Burdess <dog@b...>
  • Re: Principles of XML design
    • From: Peter Hunsberger <peter.hunsberger@g...>

• Prev by Date: Re: Principles of XML design
• Next by Date: Re: Principles of XML design
• Previous by thread: Re: Principles of XML design
• Next by thread: RE: Principles of XML design
• Index(es):
  • Date
  • Thread