Hi, this is mainly to Derrell, Victor, Andreas and Nick as authors of the PHP, Python, Java and Perl JSON-RPC Backends, but also to anyone else with an interest in the json-rpc backends. These backends are quite diverse in implementation, documentation, and development status:
http://qooxdoo.org/documentation/0.8/rpc_perl http://qooxdoo.org/documentation/0.8/rpc_java http://qooxdoo.org/documentation/0.8/rpc_php http://qooxdoo.org/documentation/rpc_python and I wonder if we should not try and make an effort to present a more coherent and better documented backend experience before the 1.0 release. I think the following points would be salient: 1) Implementation If you look through the individual implementations, they have quite different ways of actually invoking the service methods. This is due to language specificities and to the different ways the servers work (Script vs. standalone server vs. servlet container). However, I think some effort could be made to offer a more uniform way of implementation which allows users to switch backends more easily. This also touches some points Burak has recently made concerning his SOAP backend. 2) Devolopment status It would be great if all backends could have a stable release accompanying the qooxdoo 1.0 release. The java backend seems to be stable and in production, PHP has a stable release but also a trunk that is ready for release (but could also still be changed in some respects as far as point 1) is concerned). RpcPython certainly needs more testing and is also conceptually not yet 1.0. I don't know about the state of the Perl backend. 3) Documentation Well, let's say, the current state of documentation is sketchy at best (just click and see). Here, too, some coordination and common structure would certainly help users. Also, documentation should move out of the "documentation/0.8/" namespace and either into its own "documentation/backend" section or into the "contrib" section, since the servers do not move with the versioning of qooxdoo, as long as the json-rpc protocol doesn't change (that's the beauty of it all). We could discuss this here on the list or move off-list in case it is not of general interest. Cheers, Christian -- View this message in context: http://n2.nabble.com/Rpc-backend-harmonization-tp4075821p4075821.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
