On Feb 1, 12:21 pm, cd34 <[email protected]> wrote:
> On Jan 31, 1:03 am, binadam <[email protected]> wrote:
>
> > Does pyramid_rpc.jsonrpc only accept 2.0 requests? when i use android-
> > json-rpc client to make rpc call i get JsonRpcRequestInvalid
> > exception, so I'm guessing android client is sending v1.0 requests
> > (must admit I don't know difference between versions 1.0 and 2.0)
>
> There ishttp://code.google.com/p/android-json-rpc/which does handle
> 2.0, but, I suspect the library you're using is probably not sending
> the rpc_version, rather than it being 1.0.
>
> json-rpc 1.0 doesn't support named parameters and only supported
> positional parameters, so, you would pass something like:
>
> "params": ["asdf", "qwer", , , , "username"]
>
> json-rpc 2.0 would look like:
>
> "params": {"name":"asdf", "company":"qwer", "login":"username"}
>
> As you might imagine, that alone is going to be quite a showstopper.
> If commenting out that check worked, you're probably using json-rpc
> 2.0 and should be pretty safe and I suspect that is the main reason
> pyramid_rpc forces json-rpc 2.0.
Looks like android-json-rpc is doing v1.0 as seen below:
{"id":1,"method":"search","params":
[34.0149334,-118.2710851,100,-50,50]}
json-rpc 2.0 supports both named & positional parameters which is why
I'm guessing it worked after bypassing the version check.
Thanks.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
