xml-dev - Re: Issues with Packaging Application Payloads

[Aaron Swartz <aswartz@swartzfam.com>]

David Ezell <David_E3@Verifone.Com> wrote:

>> Then there's #4, the *RIGHT WAY* to do this, which is: A) Before inserting
>> your arbitrary text into your XML wrapper, run it through a filter that
>> replaces & with &amp;, < with &lt;, and > with &gt;. B) Before handing
>> arbitrary text back to the user, run it through a filter that replaces &lt;
>> with <, &gt; with >, and &amp; with &.
>> 
>> Voila, the problem is solved.  You don't have the byte bloat of base64, you
>> don't have the limitation of not including ]]> in CDATA, and you don't have
>> to mess up validation.
>> 
> Not a bad idea for simple uses, but it won't nest (at least I don't think it
> will):  the export filter would convert all the PCDATA at once.  It seems to
> me a safe bet that if you need to nest one level, you'll have use cases for
> nesting to N levels.

I don't understand -- couldn't you just use &amp;?

Original: <text/>
One level: &lt;text/&gt;
Two levels: &amp;lt;text/&amp;gt;
Three levels: &amp;amp;lt;text/&amp;amp;gt;

-- 
Aaron Swartz | me@aaronsw.com | http://www.aaronsw.com