On Fri, Nov 27, 2009 at 08:57, panyasan <[email protected]> wrote:
>
> 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:
>
Hi Christian,
I'm really glad you've recently been taking the lead on organization of
backends! It's really useful to have someone leading the charge. Thank you!
Way back when, I wrote the Backend Developers' Guide to assist others in
implementing "conforming" backends, and the RpcExample tests to "prove"
conformance. Since then there have been some minor extensions to some of the
backends, e.g. only the PHP backend supports the Remote Table example and
there is a second Error test for thrown vs returned errors, but essentially
the common functionality remains. All backends support what's in the
Developers' Guide and tested by the basic RpcExample tests. I believe this
is all that is "required" from a commonality point of view. Each backend
should be free, IMO, to use best practices in the implementation language
without regard to implementation details of other languages.
There is certainly room for expansion of the original "specification" in the
Developers' Guide, and introspection is a very reasonable addition. Since
all of the key players are involved in this discussion already, you might
describe what you've implemented in that regard in the PHP backend to see if
it is feasible to implement in the other backends.
I definitely agree on the need for documentation improvement!
Derrell
------------------------------------------------------------------------------
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
