Hello,

I am currently porting Martin's json-rpc/node code [1] to qxoo to run on the
server (as a contribution named "RpcNode"). I plan various modifications,
but want to announce the following beforehand to hear your thoughts:

In contrast to Derrell's RPC implementation [2],  the current 1.0 [3]  and
2.0 [4] specifications have no "service" parameter, but only a "method"
name. I consider this a deficiency, and so do people on the json-rpc list
[5]. There is a pending feature request to introduce an optional "service"
parameter in json-rpc version 2.1. Thus, I think it would be unwise to
remove the "service" parameter from the json-rpc implementation and break
compatibility with the existing qooxdoo json-rpc server, just to have to
re-introduce it later. I am happy to provide arguments why I think the
current spec is deficient in this regard.

I will thus implement an optional "service" parameter, which will will work
the following way: If provided, the server will try to require() a class
with the name of the service, which will have to subclass "rpcnode.Service",
if it hasn't been loaded already. If the parameter is not given, the default
service class will be used. 

Thanks,

Christian

[1] http://github.com/wittemann/JSON-RPC-for-Node.js
[2] http://manual.qooxdoo.org/1.2.x/pages/communication/rpc.html
[3] http://json-rpc.org/wiki/specification
[4] http://groups.google.com/group/json-rpc/web/json-rpc-1-2-proposal
[5]
http://groups.google.com/group/json-rpc/browse_thread/thread/89ec508665578b49/
-- 
View this message in context: 
http://qooxdoo.678.n2.nabble.com/json-rpc-node-service-parameter-tp5389154p5389154.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to