MSXML.DLL, right? This will work on NT but, doesn't help *NIX users. I feel
that an XML parser would be beneficial enough that it should be included in
CF. Right now only a portion of the developer base can make use of
MSXML.DLL. There's the OS issue and the fact that the developers need open
access to CFOBJECT. These two things will limit a lot of developers,
especially those in remotely hosted environments. Also, MSXML, while
steadily improving, is NOT 100% W3C XML 1.0 compliant. Version 3.0 Beta, the
most recent, is approx. 95-97% compliant so things look good but, it still
has some issues to resolve relating to non-existent or malformed unused
entities, attribute-value normalization, end-of-line handling, and reporting
validity constraints when running in non-validating mode. Ok, so MSXML isn't
100 compliant, so what? Well, if I use MSXML and you use Xerces (Apache
Project's XML parser) we may come up with different results. I'd rather have
everyone using one parser that is 90% compliant than 10 parsers, each of
which produces slightly different results.
Steve
-----Original Message-----
From: Benjamin S. Rogers [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 31, 2000 10:16 AM
To: [EMAIL PROTECTED]
Subject: RE: What I want in CF (was: Learning ASP)
>XML parser. Enough to check well-formedness with the option
>to validate against a DTD. It doesn't have to "execute" the XML.
If you are on NT, what about the XML Parser that comes with Internet
Explorer? Many people have been using this successfully from within
ColdFusion Apps.
Benjamin S. Rogers
Web Developer, c4.net
voice: (508) 240-0051
fax: (508) 240-0057
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
