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...
I also have JSON-RPC 1.1 working and it works great. kwparams would be a breaking change (not to mention I think "kwparams" is an inelegant identifier that...
Enter your vote today! A new poll has been created for the json-rpc group: Do we need mixed named and positional parameters? (this refers to the "suggestion...
json-rpc@yahoogroups....
May 7, 2007 5:09 pm
537
... if you know a better name: tell me. ... ok. but this would mean that you cannot mix named and positional parameters. that would be ok for me, and I already...
Hello, I noticed that the specification has not yet specified error codes. A previous msg suggested using error codes found in XML-RPC implementations. Can...
Welcome to the world of implementing draft specifications :) It's a risk you take. In my opinion nobody should worry about breaking draft implementations...
Mikeal Rogers
mikeal@...
May 9, 2007 4:51 pm
545
Hi all, I am a newcomer to the JSON-RPC 1.1 draft process. First, Is anything actually happening here? I have seen no comments from the original draft authors...
hi, ... I tried this, and created an improved working-draft (some months ago), which you can find here: http://84.16.237.14/jsonrpc/ the next steps (for me)...
Hi I'm interested in the feature of server-to-client messages, specified on the spec, but I can't find it's implementation on the python code, is anyone...
1.1 spec STILL isn't complete, and is too complex, in my opinion. An we NEED it finished, to make it enterprise-ready and beat the shit out of immeasurably...
Hi the bug tracker didn't let me post as guest/guest. there is a python error with the %-substitution. I believe what you wanted is to be able to call module...
Hey, thanks for the fix, it is checked in now. just checked trac, it did let me log in as guest/guest and it let me create a ticket (#14). Not sure why it did...
hi Jan. about trac it's probably the stupid proxy here at my office for someone reason noone knows how to configure it "right"..... anyway where you able to...
I'm in 100% agreement with 1, the spec not being finished a big problem, who is responsible for editing the spec? who are the stake holders here and can we...
Mikeal Rogers
mikeal@...
Jun 5, 2007 11:54 pm
558
WSGI ( http://www.python.org/dev/peps/pep-0333/ ) is increasingly popular among the python web community. I wrote a jsonrpc "application" that dispatches...
Mikeal Rogers
mikeal@...
Jun 6, 2007 12:18 am
559
Hey, I did have a quick look at the other mails, just have not put it in the code yet. Thanks ... where you...
Hey, ... I, Jan-Klaas Kollhof, created the 1.0 specs. Atif has been the driving force behind the 1.1 specs. Unfortunately, I have had little time in the past...
hi, ... did you read http://84.16.237.14/jsonrpc/ ? ... hmm, I don't think so. in terms of RPC, what would i.e. a string mean? that it's the only parameter to...
Hi all! I've found a small bug in the ServiceProxy class (proxy.py). The 1.1 draft spec, section 7.3 - Procedure Return Object, states that the error member...
Hi I found this a while ago and it's part of my patch at the message call "server-to-client message? and a small patch." although my path covers all of the...
... I think this should be made optional. I got a project in which I'm implementing json-rpc over tcp (I have a patched version of json-rpc.org code with it) ...
Hi I coded this a while ago for a small project I have which should get it's own server (no need for apache) If I remember correctly it doesn't depends on...
... Only json-rpc over HTTP is covered in the new spec. If you're doing it over TCP then you're free to disregard HTTP specific areas of the spec, like HTTP...
Mikeal Rogers
mikeal@...
Jun 15, 2007 1:55 am
569
... yes, but I separated HTTP from the spec in http://84.16.237.14/jsonrpc/. and I and many others think http://84.16.237.14/jsonrpc/ is a major improvement to...