JSON-RPC Google Group

Re: [json-rpc] Re: Maintainers

2010-01-07T17:52:40Z

Yeah, it a little outdated, but still alive =). I've see it.
Generally, no target language for server side. I just made very-very
simple implementation of JSON-RPC server and a few integration in
jQuery for home experiments, but a month ago i start (not actually, it
would be better to name "trying to start") write better

Re: Maintainers

2010-01-07T17:38:02Z

No "official" list as such. You can find a (outdated?) list on the old
json-rpc site:
[link]
Though I know for a fact that several are missing. Not all are v2.0
either. Google/Bing/Yahoo is probably your friend for this.
What language(s) are you looking for?

Re: [json-rpc] Re: Maintainers

2010-01-07T17:28:42Z

Thx, i meant who is maintains the implementations, sry for my english.
Is here some kind of JSON-RPC implementations list?

Re: Maintainers

2010-01-07T17:15:53Z

Yes. Anybody may know which people are the members and managers of
this group (assuming this is what you mean by "project").
If you are asking who the managers are, I think it shows in the group
details. There are currently 8 managers and ~221 members.
If you meant to ask the slightly different question of who is in

Maintainers

2010-01-07T16:47:43Z

Hi. Could anybody know who is currently maintain this JSON-RPC project?

Re: JSON-RPC 2.0 parameters: scalars only, no arrays + objects?

2010-01-05T21:51:20Z

+1 for "expected" instead of "right".
As for "scalar", I also find this somewhat confusing to describe
collectively the null, boolean, number and string datatypes. The word
"scalar" implies a quantity that cannot be resolved into components
and can vary in magnitude (scale). I don't see how null and strings

Re: [json-rpc] Re: JSON-RPC 2.0 parameters: scalars only, no arrays + objects?

2010-01-05T20:59:43Z

I'd prefer that the specification contain a definition of the term
"primitive value" and that we use "primitive" instead of
"non-structured," or "scalar."
Ideally the definition would list the primitive types, since in some
languages, e.g., "string" is a non-primitive type.
Best,
r

Re: JSON-RPC 2.0 parameters: scalars only, no arrays + objects?

2010-01-05T20:34:58Z

I agree, expected sounds better.
yeah this would make it a lot clearer, good catch..

Re: JSON-RPC 2.0 parameters: scalars only, no arrays + objects?

2010-01-05T17:00:59Z

Sounds good to me. Could we change 'right' to 'expected' in your list?
We keep using the word scalar to mean a non-structured (or non-
composite) value. But the word scalar seems to mean a great deal of
things in different contexts. As well as not having a clear meaning in
the negative, as in in non-scalar value.

Re: [json-rpc] Re: JSON-RPC 2.0 parameters: scalars only, no arrays + objects?

2010-01-05T15:06:15Z

This paragraph should be corrected (+) as follow to reflect what I
believe is intended here :
+ * by-position: params MUST be an Array, containing the VALUES
in the right order (like in JSON-RPC 1.0).
* by-name: params MUST be an Object, containing the
+ parameter-names and their VALUES. The names MUST match exactly

Re: [json-rpc] Re: JSON-RPC 2.0 parameters: scalars only, no arrays + objects?

2010-01-05T13:09:05Z

I'm not sure I get you...
Quote from the Spec/Proposal:
params
An Array or Object, that holds the actual parameter values for
the invocation of the procedure. Can be omitted if empty.

as well as:
4.2 Parameters (positional and named)
Parameters for a procedure call can be specified by-position, or

Re: Request for clarification about named and positional parameters

2010-01-05T05:58:48Z

Hi Robert,
Under "2. Conventions" it actually says
"All names (i.e. method-names or parameter-names) are case-sensitive."
~ Vladimir

Re: JSON-RPC 2.0 parameters: scalars only, no arrays + objects?

2010-01-05T05:50:27Z

Good! It's just that the spec isn't explicit on kind of parameter
values are allowed and the examples I've seen use only JSON scalars.
Sorry, yes, I meant parameter values
{
"id":0,
"method":"ldap.getEntry",
"params":{
"attributes":["cn","sn","displ ayName"],
"dn" :"uid=admin,ou=system"

Re: [json-rpc] Re: Request for clarification about named and positional parameters

2010-01-04T22:12:29Z

My suggestion would be that we can get away with nondescript as long as
we don't do anything like discovery. Once we add some kind of
introspection methods --- which seems like an obvious extension, and one
that's present in xml-rpc --- we are likely to need to be much more
clear about how a procedure advertises itself, and what is a parameter list.

Re: JSON-RPC 2.0 parameters: scalars only, no arrays + objects?

2010-01-04T20:43:50Z

I am not entirely grokking what you posted, but I don't see why it
should not work.
By method values do you mean parameters?
Perhaps an example of what your json-rpc request string looks like
would clear this up?