I'm not entirely sure what the xml-rpc spec says, but
I've found that in py-xmlrpc there is a (seemingly to
me) arbitrary limit on the number of parameters that
get passed. If a remote function has six parameters,
py-xmlrpc clients freak because the two extra
parameters are begin interpreted as something
else...this also seems to be a possible security hole.
Logged In: YES
user_id=184164
The is due to incorrect use of the execute function. This
xmlrpc interface differs a bit from others in that the
arguments are passed as a list:
client.execute('someMethod', ['arg1', 'arg2', 'arg3'], 3.0)
The reason is that the last timeout-arg is optional.