According to JSON RPC 1.1, the Service Description object (response to
system.describe procedure call) MUST contain an "id" member which "uniquely
and globally identifies the service." Furthermore, the "string MUST use
the URI Generic Syntax ...". It seems that json-xml-rpc treats this "id" -
if received by a server - like the optional "id" in an ordinary response to
a procedure call resulting in misbehaviour as it cannot associate the
Service Description object with the procedure call.
Original issue reported on code.google.com by Robin.Ha...@googlemail.com on 25 Jun 2008 at 3:17
Original issue reported on code.google.com by
Robin.Ha...@googlemail.com
on 25 Jun 2008 at 3:17