On Jan 19, 2010, at 16:52 , Fabian Jakobs wrote: > Hi, > > thank you for the valuable feedback. We plan to work on the RPC client > in the new future. This is what we have in mind right now: > > Our goal is to build a JSON-RPC client, which fully implements the > JSON-RPC protocol version 1 and 2 without any proprietary protocol > extensions. We think proprietary protocol extensions make it much harder > to implement complaint backends and to be interoperable with existing > JSON-RPC implementations. yes.
> JSON-RPC version 2 support is interesting > because it adds support for batching requests and named parameters. > > Specific deficiencies of the current implementation are: > > - it only supports JSON-RPC version 1 > - it adds an proprietary "service" argument to each request, which is > supposed to select the service. The standard way would be to > differentiate services by their URL end points. > - cross domain support is proprietary. We have to investigate the right > way to do this. > - non JSON compliant encoding of dates. We feel that de-/encoding of > complex data types like dates is in the domain of the application > developer and should not be part of the transfer protocol. > > The consequences for the backends would be: > > - The "service" argument should be ignored OK and replaced the argument by URL end point as it sound like JSON standard RPC. Am I right ? (I never read JSON RPC spec). > - encode dates as valid JSON OK. > - optional support for cross site requests OK for optional behavior. > > What are your ideas about this? What about version 2 new features ? - What about what you called "batching request" ? I don't know what it is but it look like part of the spec ? - Named parameter will make it difficult and probably impossible for backend language where method parameter are passed only by position like Java. We might design some annotation for that but it would break backend simplicity as currently, for a Java backend, nothing special is needed. So, for named parameter features, I would ask for more information. > > Best Fabian > > -- > Fabian Jakobs > JavaScript Framework Developer > > 1&1 Internet AG - Web Technologies > Ernst-Frey-Straße 9 · DE-76135 Karlsruhe > Telefon: +49 721 91374-6784 > [email protected] > > Amtsgericht Montabaur / HRB 6484 > Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas > Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver > Mauss, Jan Oetjen > Aufsichtsratsvorsitzender: Michael Scheeren > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
