thron7-2 wrote: > > AFAICT, the Python RPC hasn't been touched for a while. If you look at > [1], you'll see that the compatible qooxdoo versions are 0.8 and > 0.9-pre, so chances are the server implementation is not fully > compatible with the current client classes. > > If you stick with the Python RPC it might be necessary that you apply > patches to make it conformant with qooxdoo 1.1.x. The RpcExample contrib > contains the (famous) SERVER_WRITER_GUIDE, which should be of further > help to tackle the server side of things (I hope this one is up-to-date). >
AFAIK, the JSON-RPC Protocol (in its qooxdoo-version) has not changed since qooxdoo 0.8, so I don't think any changes are necessary on the backend-side of things, and, if you use the qx.io.remote.Rpc class with its standard API, I wouldn't know of any changes there either. The python implementation is simply unmaintained, but when I checked it in as a contrib, everything worked well. Try the RpcConsole contribution as suggested (http://qooxdoo.org/documentation/RPC_Python) to test the backend and please report the errors that are thrown, then we might be able to help. Cheers, Christian -- View this message in context: http://qooxdoo.678.n2.nabble.com/General-question-tp5247622p5254139.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
