Derrell Lipman wrote: > > Jean-Baptiste, the reason that a hasCapabilities() method is required is > that a backend can be used by/for multiple applications. The backend need > not be updated on the same schedule as the applications (except for adding > the requisite backend methods, of course). This new method allows new > applications to determine if the backend is as new as it is, i.e. it has > all > of the capabilities that it would like to use, or if it must limit its > functionality because an older backend is still in use. >
... to support Derrell's point and finish my own argument: if a json-rpc backend is used as a general webservice that is queried by more than one application, there must be a way the client application can determine what to expect from the backend. So my proposal would be to add one single service method that returns information on the server's general capabilities, in some ways, the "interfaces" offered by the server. I am thinking along the following lines: http://qooxdoo.org/documentation/jsonrpc_extensions#getcapabilities The rationale for this is to offer information not only on the name of the feature, but also its version and an url to more information. If a server maintainer does not see any need to bother with this, the only thing I would like ask from him/her would be to impement the service method to simply return an empty object ({}), then this would not break the client request. All other extensions to the core json-rpc server behavior would be completely optional. Does that make sense to you? C. -- View this message in context: http://n2.nabble.com/Rpc-backend-harmonization-tp4075821p4080740.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
