Derrell Lipman wrote > This sounds like your service implementation isn't really implementing > JSON-RPC, or I'm not understanding your issue. JSON-RPC *requires* that > there be an *id* field (or that it be missing, in which case it's a > "notification"). It can't be any other name. Here's the JSON-RPC spec, > with > which the qooxdoo Rpc class is conformant (but not complete, e.g., no > batch > requests): http://www.jsonrpc.org/specification > > If I'm just not understanding your question correctly, please let me know. > > Derrell
This is my original question: /This works fine. Only my service returns a result with a 'tid' instead of an 'id'. Unfortunately, the 'id' property is hard coded in the framework to process the result. It would be nice if this was configurable, so, it would be possible to process results with, for example, a 'tid' instead of a 'id'./ So, there is an *id* field, only the field is called *tid*. This is because the service was meant to work with ExtJs, and for that framework, the reply should be identified by a 'tid' instead of an id (probably the t is for transaction). I don't want to change the backend otherwise I bread the service for my current ExtJs implementation. -- View this message in context: http://qooxdoo.678.n2.nabble.com/qx-io-remote-Request-51-1-Received-id-undefined-does-not-match-requested-id-tp7586683p7586713.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
