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

RE: Tradeoffs of XML encoding by enclosing all content in CDAT

• From: "Michael Kay" <mike@s...>
• To: "'Andrew Welch'" <andrew.j.welch@g...>,"'Karr, David'" <david.karr@w...>
• Date: Mon, 29 Sep 2008 16:51:44 +0100

> You often get this problem when people write XML as a string 
> rather than using a proper XML Writer...
> 
> For example:
> 
> xmlStr = "<foo>" + someVal  + "</foo>";
> write(xmlStr);
> 
> The are several problems with this approach, one being that 
> ampersands won't be escaped properly.

I've also seen such code result in a performance bottleneck. It turned out
that generating the XML was taking significantly longer than subsequent
parsing, validating, and transforming of the same XML. It's much more likely
to be optimized if you use a library that has been carefully written by
someone else.

Michael Kay
http://www.saxonica.com/

• References:
  • Tradeoffs of XML encoding by enclosing all content in CDATA blocks
    • From: "Karr, David" <david.karr@w...>
  • Re: Tradeoffs of XML encoding by enclosing all content in CDATA blocks
    • From: "Andrew Welch" <andrew.j.welch@g...>