kereszt_hu a écrit :
>
>
> 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?
>
> Is there any way to keep XML in parameters un-encoded.. and so human
> readable? eg. <xml> value "type"?
>
> 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.
>
> Thank you
> Laszlo
>


















There is no way, to send unescaped xml, sorry.
It is not the fault of xmlrpc, it is the fault of the xml spec _ you
cannot ever use a "<" char inside a block of text in xml - there would
be no sensible way for the parser to know that that char is not the
start of a new element.
Normally the xmlrpc library you are using takes care of the encoding for
you, so that you do not have to take care of it, neither when sending
nor when receiving strings.
Otoh if you plan to send binary data, you might be sending something
that will not be properly escaped and thus invalid in the charset you
are using. Better base64-encode in that case.
If you are writing your own xmlrpc library, please stop and pick one of
the many existing ones.


bye
Gaetano


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