[Asterisk-Dev] Manager XML

[Kevin P. Fleming]

Colin Anderson wrote:

> the "Encoding" part takes care of 90% of those issues for you, most XML
> parsers will have no problem with this. Ran into the same issue when I was
> doing an XMLRPC implementation to transmit purchase orders to a business
> partner. Our database had loads of those "illegal" chars and adding the
> "encoding" part took care of it.

That may be true, but it does not produce well-formed XML. There is no 
reason to produce a non-conforming XML implementation at this point in 
the game... otherwise we risk people using compliant parsers choking on 
our output. When the output's destination is well known, that is safe. 
When it's not, I don't think that's a good idea.

There is a small XML library at

http://www.easysw.com/~mike/mxml/index.php

It's under the GPL, though, so it can't be integrated into the tree, but 
it would be a very good candidate for producing conforming XML output.