I ve been using XmlRpc++ in the server side and XML-RPC.NET in the client side for a couple of days and I noticed that there are some problems with the handling of "empty" tags. For example I want to send an empty array i.e. an array with length 0 and the client sends it as "<data />" but the server (XmlRpc++) does not parse that correctly. Instead it expects "<data></data>". The same is also true for strings where an empty string is sent as "<string/>" but the server refuses to parse it.
I am not sure whether the specification of xml-rpc permits these "compact" forms of empty tags but based on my knowledge of XML I would say that the client has every right to use them. I checked the source code of XmlRpc++ and indeed it seems very strict in what it accepts.
Any comments?
Cheers
Stelios
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also discover this bug in process of parsing result from one of ours xmlrpc servers written in php. This issue is fixed in my local copy of XmlRpc++, but I have no idea where to post publish this fix.
Best Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
I ve been using XmlRpc++ in the server side and XML-RPC.NET in the client side for a couple of days and I noticed that there are some problems with the handling of "empty" tags. For example I want to send an empty array i.e. an array with length 0 and the client sends it as "<data />" but the server (XmlRpc++) does not parse that correctly. Instead it expects "<data></data>". The same is also true for strings where an empty string is sent as "<string/>" but the server refuses to parse it.
I am not sure whether the specification of xml-rpc permits these "compact" forms of empty tags but based on my knowledge of XML I would say that the client has every right to use them. I checked the source code of XmlRpc++ and indeed it seems very strict in what it accepts.
Any comments?
Cheers
Stelios
I also discover this bug in process of parsing result from one of ours xmlrpc servers written in php. This issue is fixed in my local copy of XmlRpc++, but I have no idea where to post publish this fix.
Best Regards