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


On Fri Jan 16 2015 at 6:41:02 AM halcwb <hal...@gmail.com> wrote:

> I have this override f the qx.io.remote.Request:
>
> [CODE]
> qx.Class.define "informedica.io.remote.Rpc",
>   extend: qx.io.remote.Rpc
>
>
>   statics:
>     _URL: '../../../DirectRouter/Index'
>
>     _rpc: -> new informedica.io.remote.Rpc()
>
>     ###
>     Perform an RPC with
>     @param service {String}: the service to be used
>     @param method {String}: the method to be called
>     @param callback {Function}: the callback function
>     @param params: a list of comma separated parameters
>     ###
>     callRpcServer: (service, method, callback, params...) ->
>       me = informedica.io.remote.Rpc
>
>       url = me._URL
>       rpc = me._rpc()
>       rpc.setTimeout 10000
>       rpc.setUrl url
>       rpc.setServiceName service
>
>       rpc.callAsync.apply(rpc,  [callback, method].concat params)
>
>
>   construct: ->
>     @base arguments
>
>
>   members:
>
>     createRpcData: (id, method, params) ->
>       data = if params.length > 0 and params[0]? then params else null
>
>       request =
>         action: @getServiceName()
>         method: method
>         id: id
>         data: data
>         type: 'rpc'
>
>       request
> [/CODE]
>
> 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'.
>
>
>
> --
> 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-tp7586683.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
>
------------------------------------------------------------------------------
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

Reply via email to