Hi James,

I'll update the results on my web site, at least. I'll forward separately a
couple of emails from the JDOM list discussing how XMLS could be made the normal
serialization method while still allowing people to use default serialization if
they want (useful if they're associating extra information with the document
components and aren't too concerned about performance).

I think the whitespace option I mention at the end of the dW article is
something to consider, too. The idea here is to allow applications to discard
isolated whitespace (whitespace that's not embedded in non-whitespace) as the
document is parsed. For middleware applications this type of whitespace is only
there to make the documents readable and is ignored by the application.

Electric XML has been discarding it all along, apparently without anyone
noticing before. That's not a good approach, since it breaks handling of some
types of documents (and violates the XML recommendation). Making this an option
under the application's control seems a good alternative. It'd be even better if
it could be implemented in the parser rather than the document model.

  - Dennis

James Strachan wrote:

> Hi Dennis
>
> Great article! Thanks for the link - I was wondering when the new article
> would show up :-)
>
> Have you any plans to follow this article up showing the effects of your
> XMLS work on the serialization graph? Certainly as soon as I've a few cycles
> I want to make your XMLS the standard serialization mechanism for dom4j.
>
> James
> ----- Original Message -----
> From: "Dennis Sosnoski" <[EMAIL PROTECTED]>
> To: "dom4j-dev" <[EMAIL PROTECTED]>
> Sent: Thursday, October 04, 2001 9:45 AM
> Subject: [dom4j-dev] Java document model performance
>
> > My article on Java document model performance is available on IBM XML
> > developerWorks, at
> > http://www-106.ibm.com/developerworks/xml/library/x-injava/index.html This
> has
> > the results from performance tests run at the end of July. I'll update my
> site
> > with new results in early November, so if there's a new release of dom4j
> by then
> > I'll try it out.
> >
> > dom4j did very well in the tests.
> >
> > For the next run I'll add a set of small documents to the performance
> tests.
> >
> >   - Dennis
> >
> >
> > _______________________________________________
> > dom4j-dev mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/dom4j-dev
> >
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
> _______________________________________________
> dom4j-dev mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dom4j-dev


_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-dev

Reply via email to