Hello Derrell,
Derrell Lipman wrote: > > 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. > Yes, this is certainly the way to go. No matter how the backend is functioning internally, the behavior should be exactly the same from the perspective of the qooxdoo (or any other javascript-based) application on the client. And this is why a test suite like RpcExample is so important. This is what we should concentrate on and where I think all backend implementators can agree on. Your server-writing-guide (http://qooxdoo.org/documentation/0.8/rpc_server_writer_guide) should be the basis of that. Here are some suggestions: - The "Server writer guide" should be made a "Standard" - There should be a clear normative "core" (obligatory to pass the standard) and optional "extensions" - We should create a page with "proposals" to this standard (core / extensions) and then discuss the pros and cons of the proposals together. Derrell Lipman wrote: > > 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 would do that as an extension proposal. However, there should be one "core" feature that allowed to query the server whether a certain extension is available. Best, Christian BTW the page http://qooxdoo.org/documentation/RPC is referenced in various places in the wiki but doesn't exist. -- View this message in context: http://n2.nabble.com/Rpc-backend-harmonization-tp4075821p4076296.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
