On 2 Jun 2009, at 15:24, kereszt_hu wrote:

> After digging up the posts I decided to ask..
>
> According to XML-RPC spec, parameter value of <string> cannot
> contain < or &. This means, sending XML as a parameter should be
> escaped. Even though, it is going to be part of another XML. Am I
> right?

Yes, implementations generally use &lt; and &amp;
>
>
> Is there any way to keep XML in parameters un-encoded.. and so human
> readable? eg. <xml> value "type"?

Yes, the text can be enclosed in a CDATA section:

<![CDATA[ some text with < and & ]]>

I'd be slightly nervous about using CDATA sections as some
implementations of XML-RPC have used very simple code to parse the XML
and may not be able to understand the construct.

>
>
> Maybe, I've gone too far. Please, clarify me either how to pass XML
> as a parameter value or XML-RPC is not for this use and I must crack
> down to simpler parameters or encoded (xml or base64) values.

What XML-RPC implementation are you using? I would expect the
implementation to accept and correctly substitute the < and &
characters in string parameters.


John Wilson




[Non-text portions of this message have been removed]