xml-dev - Re: IE5 Parser

["Richard Anderson" <rja@arpsolutions.demon.co.uk>]

Hi,

My use of IE5 MSXML has shown it to be very fast and generally the best XML
parser available around if you're using IE on the client or server and want
to load the entire doc into mem etc.

The ActiveDOM parser (http://www.vivid-creations.com/dom/index.htm) from
Vivid is essentially a simpler version with the same interfaces, but it
doesn't need IE to be installed.  ( XSL + validation is coming later in the
year)

Cheers,

Rich.
----- Original Message -----
From: Hunter, David <dhunter@Mobility.com>
To: 'John Evdemon' <John_Evdemon@freddiemac.com>; XML Developers
<xml-dev@ic.ac.uk>
Sent: 8 July 1999 16:46
Subject: RE: IE5 Parser


> > From: John Evdemon [mailto:John_Evdemon@freddiemac.com]
> > IE5's parser is designed for client-level parsing since it
> > was imbedded in the
> > browser, correct?
> >
> > This implies (at least to me) relatively high-risk -- the
> > parser's performance
> > on a back end server is an unknown.
> >
> > Has anyone seen/done any benchmarks?
> >
> > Can it handle the volume?
> >
> > Thanks!
>
> I'm not sure if the MSXML parser was designed with the client in mind or
not
> - I recall hearing somewhere that someone at Microsoft was annoyed that
> MSXML was so closely tied to the browser, since it was <em>meant</em> for
> the server.  (This recollection of mine is not necessarily accurate,
> however, and even if it is it's only hearsay.)
>
> But in the project I'm on now we use it on both client and server.  Most
of
> our inter-component communication is done via XML, and there's quite a
bit,
> so MSXML is doing a pretty good job there.  (Sorry, no numbers.)  There is
> also a daily batch job that runs, where our server-side MSXML component is
> processing a largish XML file (somewhere between 400 and 600K), and it's
> having no troubles with that.
>
> Not exactly concrete proof one way or the other, but for our needs MSXML
is
> doing well on the server, and I haven't seen any scaling problems yet.
> Someone else might have better numbers for you, though.
>
> David Hunter
> david.hunter@mediaserv.com
> MediaServ Information Architects
> http://www.MediaServ.com
>
> xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on
CD-ROM/ISBN 981-02-3594-1
> To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
> (un)subscribe xml-dev
> To subscribe to the digests, mailto:majordomo@ic.ac.uk the following
message;
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
>


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)