OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   [Fwd: Sun XML early access]

[ Lists Home | Date Index | Thread Index ]
  • From: "Simon St.Laurent" <simonstl@simonstl.com>
  • To: XML-Dev Mailing list <xml-dev@ic.ac.uk>
  • Date: Sat, 26 Sep 1998 07:51:48 -0400

Forwarded for David Brownell:

Tyler Baker wrote:
> The SAX support is solid and the only SAX Parser that is faster that I am
> of is XP.  This is understandable since I have personally found that XP's
> routines are tons faster than the java.io classes which the SUN Parser uses.

I/O is only one factor.  I think you'll find that diagnostics are much more
useful from Sun's parser.  If we hear performance is an issue, we can put
more work into that, too.

Comparing validating parsers is also interesting.  I don't think there's a
faster validating parser, in 100% Pure Java, generally available today.

> Everything in the com.sun.xml.tree package (including the DOM support) is
> implemented (and that is a claim I make without even looking at the source).
> When parsing Jon Bosak's ot.xml I get out of memory errors on the second
> even after trying to reclaim memory from the first try (I had to write my
> benchmarks as the there were none supplied.).  Besides the memory problems,
> building the DOM tree is incredibly slow.  Better off to stick with
> else like Docuverse for now.

The release notes point out that object model support hasn't been tuned
for space utilization; that's different from "poorly implemented"!  And
along the same lines, this is "early access" -- as in, alpha test, so
honest bugs are to be expected.  (Report them to the feedback alias.)

Since it doesn't maintain any static state, I'd suspect that your benchmark
is saving something which causes that error.  If not, we'd certainly fix
such a bug in our code!

> The package is pretty much just SAX and DOM support and some experimental
> dealing with beans.

"Pretty much" -- but do look at the rest.  It supports the current draft
of XML namespaces, and lets you write DOM objects out as XML text (which
DOM doesn't provide).  DOM doesn't give access to the ID attribute of a
node (unless you know what DTD it's using!), so you can't implement full
XSL or XPointer with just DOM.  And there's more.

- Dave

Simon St.Laurent
Dynamic HTML: A Primer / XML: A Primer
Cookies / Sharing Bandwidth (November)
Building XML Applications (December)

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/
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)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS