Talk:JSON-RPC: Difference between revisions
→Implementations: additional parameters |
→Using TCP/IP sockets: new section |
||
Line 38: | Line 38: | ||
(http://qooxdoo.org/documentation/general/rpc/jsonrpc_introspection) The Introspection extension can describe methods. <span style="font-size: smaller;" class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/24.20.226.39|24.20.226.39]] ([[User talk:24.20.226.39|talk]]) 14:45, 9 March 2012 (UTC)</span><!-- Template:Unsigned IP --> <!--Autosigned by SineBot--> |
(http://qooxdoo.org/documentation/general/rpc/jsonrpc_introspection) The Introspection extension can describe methods. <span style="font-size: smaller;" class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/24.20.226.39|24.20.226.39]] ([[User talk:24.20.226.39|talk]]) 14:45, 9 March 2012 (UTC)</span><!-- Template:Unsigned IP --> <!--Autosigned by SineBot--> |
||
== Using TCP/IP sockets == |
|||
Not sure why the *Usage* section mentions that support of TCP/IP sockets started at version 2.0. The [http://json-rpc.org/wiki/specification JSON-RPG spec 1.0] section 2.1 already mentions "the use of TCP/IP socket streams". |
Revision as of 16:02, 5 November 2014
Computing Stub‑class | |||||||||||||
|
Example
As someone has pointed out, the example for JSON-RPC is outdated. I don't know exactly what has changed with JSON-RPC, but I think it would be more reader-friendly if someone with a bit more experience with JSON-RPC would correct it. Quartz (talk) 23:26, 26 January 2008 (UTC)
Updated examples
I have added examples for the current release (1.0) and for the proposed specification (2.0).
If anyone has the time for it, the bullet list under "Implementations" could be made into a nice table and extended with more implementations (there is a richer list on the official JSON-RPC homepage).
--Clausc (talk) 15:48, 14 May 2008 (UTC)
WDSL equivalent: SMD?
What is the WSDL equivalent for JSON-RPC?
There is something called SMD, which means - depending on which source you consult - "Simple Method Description" (http://groups.google.com/group/json-rpc/web/simple-method-description-for-json-rpc-example) or "Service Mapping Description" (http://groups.google.com/group/json-schema/web/service-mapping-description-proposal) but the sources disagree on the syntax. --AndreKR (talk) 23:51, 5 May 2009 (UTC)
- take a look at JSON-WSP — Preceding unsigned comment added by Jakobsg (talk • contribs) 09:45, 28 February 2011 (UTC)
Versions
Someone could write a few more descriptive sentences to each version. Currently it's too short to be useful. thanks. --188.99.245.106 (talk) 14:40, 18 February 2011 (UTC)
Implementations
Perhaps it'd be clearer if the implementation were ordered by the programming language. --178.2.90.28 (talk) 13:54, 15 April 2011 (UTC)
I cleaned up the implementations list a little (e.g. removed doubles, corrected links) and removed a few unmaintained/outdated projects. --greip (talk) 09:59, 12 June 2012 (UTC)
Additional parameters
Many of implementations are not complete (like when there is only a server or only a client, no batch calls, etc) or implementations are restrictive (transport-dependent). So I suppose it's the reason to add columns to the table such as "completeness of implementation" and "transport-dependency".
And maybe it will be better to move that table to another page, like "comparison of JSON-RPC implementations". 91.77.140.144 (talk) 06:18, 21 March 2013 (UTC)
Extensions
(http://qooxdoo.org/documentation/general/rpc/jsonrpc_extensions) Qooxdoo defines a service to list JSON-RPC extensions.
(http://qooxdoo.org/documentation/general/rpc/jsonrpc_introspection) The Introspection extension can describe methods. — Preceding unsigned comment added by 24.20.226.39 (talk) 14:45, 9 March 2012 (UTC)
Using TCP/IP sockets
Not sure why the *Usage* section mentions that support of TCP/IP sockets started at version 2.0. The JSON-RPG spec 1.0 section 2.1 already mentions "the use of TCP/IP socket streams".