It appears that even 1.0 spec (http://json-rpc.org/wiki/specification)
allows for non-array result values. Maybe there was a confusion with the
fact that in v1 only a list is valid for the request parameters.
On Thu, Jan 31, 2013 at 2:04 PM, Matthew Williams wrote:
> In that case, should there be
In that case, should there be a patch that skips that for v2? Or perhaps
just raise an error for versions < v2 if the function does not return a
list? Of course, this wouldn't be backwards compatible which might be
problematic.
On Thu, Jan 31, 2013 at 1:45 PM, Laurens Van Houtven <_...@lvh.cc> wro
On Thu, Jan 31, 2013 at 4:43 PM, Matthew Williams wrote:
> I have a couple questions regarding txjsonrpc (
> https://github.com/oubiwann/txjsonrpc/) in connection with the recent
> addition of version 2.0 support.
>
> * How complete is the version 2.0 support? I had actually tried some years
> ago
I have a couple questions regarding txjsonrpc (
https://github.com/oubiwann/txjsonrpc/) in connection with the recent
addition of version 2.0 support.
* How complete is the version 2.0 support? I had actually tried some years
ago to add v2.0 support, but gave up due to some issues I no longer full
On Wed, 30 Jan 2013 23:32:34 +0100
Angelo Dell'Aera wrote:
> On Wed, 30 Jan 2013 11:04:36 -0800
> Glyph wrote:
>
> > Any volunteers for parts of this process?
>
> I'm not familiar with Twisted patching process and for this reason
> I'm just attaching a small patch here for #6245 because I'd li
