... This was met with deafening silence. I would like to keep this proposal in play. Remember, the whole point of this exercise is to enable method calls in...
Hi, I'm one of the developers working on a new project called JSON- Cache. It is a light weight persistent cache built on top of a pure Java based database...
... Has any effort been made to either improve JSON to support references, or to define an extension to allow for references to preserve object graphs (and,...
Given that JSON-RPC is based upon JSON which only can use JavaScript literals, there isn't a way to represent references natively as a JavaScript literal....
... Yep, you cant feed any graph from memory to a routine made for encoding only directed acyclic ones and expect correct result. But : reference is a matter...
Could we get by with even less? Perhaps replace cyclic references with JavaScript "pointers" marked with a special prefix, such as "$jref:this.a[0]". Consider...
... [Pete] Yep, that is understood, but what I'm getting at is that for RPC, the current JSON encoding is not really robust enough and extension need to be...
... I insist JSON is robust enough ... no extension to JSON is needed. ... Arrrrright! Conventions are everything :) What you'd like is something like this : ...
... Interesting idea. An alternate is to make the reference value an integer that numbers the ordinal position of the object in the depth first traversal of...
hi, I like JSON-RPC 1.0: it's nice and simple. And its *simplicity* is its major advantage to all other rpc-systems. The JSON- RPC 1.1WD then added some very...
I prefer this over the current 1.1WD, but that probably is not too surprise to the group. Got quite a few projects that use the 1.0 spec in production and the...
For the most part me too.. I don't like: "HTTP GET is discouraged. And if you *really* want to use HTTP GET, you should use a small wrapper, which converts...
Multiple signatures are very useful, at least I took heavily adavantage of it in xmlrpc. Adding it to the standard does not mandate that any single exposed...
hi, ... I already thought about multicall, but forgot to add some comments about it to my website. there are several different ways, multicall could be...
... The *only* "HTTP GET"-specification in JSON-RPC that would be "ok" (in my opinion), would be the same as for HTTP POST and every other protocol: "Tunnel it...
I prefer #2, as I do not see the single error to a collection of requests as an issue. The same out of procedure error issue can happen with a request that is...
I prefer #2, as I do not see the single error to a collection of requests as an issue. The same out of procedure error issue can happen with a request that is...
hi, I like JSON-RPC 1.0: it's nice and simple. And its *simplicity* is its major advantage to all other rpc-systems. The JSON-RPC 1.1WD then added some very...
... What is wrong with mixed named and positional parameters? def myFunc(param1,param2,debug=False,verbose=1): [...some cool code...] return result I see that...
... Sorry, imho it is a confusing feature in general, and it is not implemented consistently across languages / environments myfunc('hello', firstparam =...
... I know that in python, these issues are handled as exceptions and/or syntax errors. This mixed model is not confusing in python. The convention is that...
hi, ... it's complicated and not really useful. and it adds new errors. ... I hope you don't really use "param1" and "param2" as parameter-names... ... that's...
... and so, "mixed and positional parameters" add new error-cases which do not exist without them, and which are probably confusing for some programmers/users....
hi again, (answering myself ;)) ... but unfortunately, to be able to make this translation, the client would have to know the methods and its parameter-names....
hi, I now updated my 1.1WD suggestion/specification. I especially added "kwparams" and multicall. see: http://84.16.237.14/jsonrpc/ Any comments are greatly...
... Hi, Roland This is an improvement, IMHO. I'm guessing that you are just checking whether people are actually reading the thing, but you have "params"...
So the only bad thing is that by adding kwparams and removing the named arguments capability from params is that it is a pretty big change if you've already...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
