Handle <undefined>undefined</undefined> in server response

[czerwinskilukasz1]

Sample server response which was not handled before this fix:

<?xml version="1.0"?>
<methodResponse>
<params>
<param>
<value><struct>
<member>
<name>task_id</name>
<value><string>56c66c8afbc8c16bd18641c6</string></value>
</member>
<member>
<name>answer_id</name>
<value><string>0a32d8d0-a2bc-42bd-8599-6764c31ff775</string></value>
</member>
<member>
<name>url</name>
<value><undefined>undefined</undefined></value>
</member>
</struct>
</value>
</param>
</params>
</methodResponse>

[gggeek]

Sorry, but I must have missed the version of the spec or the proposed extension where the 'undefined' xml element is mentioned.

I suspect that the presence of 'undefined' might be the result of bad coding in the app using the library (or in the remote xmlrpc server), and that it should be fixed there.

Can you provide me with a pointer?