Hi everybody, I've been playing with JSON-RPC on Catalyst (http://www.catalystframework.org) for a while, but it no longer does all that I need so I've started...
In order to solicit some community consensus or sentiment, I'd like to be able to use the polls facility available to this group. Since not everyone has the...
Hi Folks, After months of head-scratching, several stalls and restarts, battles of the heart and the mind and constant hunts for spare time slots, I'm glad to...
Thanks, Atif and Jan-Klaas! You have done a wonderful job with the WD. It looks great! I will have a few questions / nit-picks. Presuming that several...
I think the for 'Object Extensions' we should stick to the 'standard' 'x-extension' format because using '$extension' already has a meaning in many languages...
... I agree and the consequences are even more pronounced once you consider query-encoding with HTTP GET. ... Nitpicking is good at this point in the spec's...
Atif Aziz, Jan-Klaas Kollhof: Thanks for the great job on json-rpc spec. There is just 1 request on my wish list; I would like to see an optional field for...
Hi Jeffery, ... Why do you feel each and every call needs to indicate the version number of the interface? Do you have a concrete scenario in mind that is not ...
So, the scenario i'm thinking of is the second case, where the server revs to v2 and the client is still v1. The clients may not know that the server changed...
I promised a few quibbles. GET seems troublesome. There seems no way in WD1.1 to distinguish a GET that wants a JSON response from a GET that wants a JSON-RPC...
I wonder if in that case the right solution wouldn't be to simply send back the data from the "result" member of the Procedure Return Object (and the "error"...
I just realized a problem with what I proposed earlier. FWIW, JSON text cannot be composed of a single String, Number, Boolean or Null value. It must be either...
... I would like to back up Jim's problem statement. When a request arrives to the server, it must be possible to decide if we have a JSON-RPC request or not...
Balazs Ree
ree@...
Sep 7, 2006 5:51 am
319
Sections 6.6 and 6.6.1 are probably more relevant for this discussion because that's what allows your case of optional versus required parameters to pass. I...
Atif, Thank you for the response. I was just thinking in terms of how the data is likely to be used. "system.describe" is a MUST for a conforming JSON-RPC...
Point taken, Jim. I agree that there may be room for misunderstanding. I'll see what I can do to improve the wording or discussion around that topic. Perhaps a...
... 1.1 WD only specifies "application/json" as an Accept parameter in the header to distinguish this from any other GET. Would "application/json-rpc" be a...
Hi Atif, ... It *is* also about content negotiation. If a client requires a json-rpc response it won't accept a non-json-rpc response and vice versa. But I can...
Balazs Ree
ree@...
Sep 11, 2006 12:05 pm
324
I found the following comment in the new draft: Atif Aziz: Strictly disallow the use of cookies. Disallowing cookies will make it impossible to use JSON-RPC...
... Why not just leave this outside of the spec, instead of `must`? I definitely see lots of places where sessions would to be started outside of the rpc call...
Matt
WickedLogic@...
Sep 14, 2006 2:39 am
326
Matt + Wilfred, I wouldn't that note to heart. It was put in there to provoke some reaction and I have that reaction now. :) I'll be removing it moving forward...
... Hi, Atif Nice to hear! I was wondering about that comment as well. Do you see an important distinction between a JSON-RPC "Service" and JSON-RPC as a...
Jim, Perhaps I'm missing a finer point here. If a json-rpc service is listening, it either gathers what it needs from the environmental variables just like the...
Matt
WickedLogic@...
Sep 14, 2006 2:18 pm
329
I agree with what you are saying, because ideally the service should function with all of it's requirements being fulfilled in the request channel and not rely...
Matt
WickedLogic@...
Sep 14, 2006 2:33 pm
330
... That would be nice, except, From 6.3.1 in the WD, "The client MUST NOT use the JSON syntax for the parameter values." and "It is specifically not possible...
On 9/14/06, Jim Washington <jwashin@...> wrote: That would be nice, except, ... Would someone be willing to go over the reasons behind not being able to...
Matt
WickedLogic@...
Sep 14, 2006 3:51 pm
332
Hi, it seems the current WD does not allow the specification of the structure of complex data types as parameter or result, basically because there is no way...
Andreas Hofmeister
andi@...
Sep 15, 2006 3:44 pm
333
Hi Balazs, It's really a hard problem to solve entirely through Content-Type anyhow. The spec suggests "application/json" because that is the best-fit...
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.
