Support v1.0 JSON-RPC Spec
Bug #456441 reported by
Duncan McGreggor
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| txJSON-RPC |
In Progress
|
High
|
Duncan McGreggor | ||
Bug Description
The current JSON-RPC implementation in txJSON-RPC is from work done prior to the adoption of a 1.0 version of the JSON-RPC spec. I believe the 1.0 spec is outlined here, such that it is:
http://
txJSON-RPC needs to be examined for compliance with this; if it's not compliant, a new client/server version needs to be implemented.
Related branches
lp:~jerith/txjsonrpc/add-id-to-response
- Duncan McGreggor: Pending requested
-
Diff: 181 lines (+42/-17)5 files modifiedtxjsonrpc/jsonrpc.py (+13/-7)
txjsonrpc/netstring/jsonrpc.py (+2/-1)
txjsonrpc/test/test_jsonrpc.py (+3/-3)
txjsonrpc/web/jsonrpc.py (+7/-6)
txjsonrpc/web/test/test_jsonrpc.py (+17/-0)
| Changed in txjsonrpc: | |
| assignee: | nobody → Duncan McGreggor (oubiwann) |
| importance: | Undecided → Medium |
| Changed in txjsonrpc: | |
| milestone: | none → 0.4 |
Revision history for this message
| Duncan McGreggor (oubiwann) wrote | #1 |
| Changed in txjsonrpc: | |
| status: | New → In Progress |
| importance: | Medium → High |
Revision history for this message
| Duncan McGreggor (oubiwann) wrote | #2 |
Revision history for this message
| Matt (posita) wrote | #3 |
To post a comment you must log in.
The payloads are now sending version 1 keys. Most payload values are working, except for the ids (which haven't been implemented yet).