4 commits

Author	SHA1	Message	Date
Quinn Slack	c0f3aff61f	remove incorrect special handling of null results ... It is not correct in general to convert null results in JSON-RPC 2.0 responses to `{}`.	2017-01-22 15:34:08 -08:00
Keegan Carruthers-Smith	7e53931322	Use correct format string for ID ... Audited all calls for Printf. Noticed the following in some logs ``` jsonrpc2 handler: sending response {1 %!d(string=) %!d(bool=false)}: jsonrpc2: connection is closed ```	2016-11-14 21:17:22 +02:00
Nico Tonozzi	2e4214c77b	Send something over the wire for responses ... I accidentally made this change in the main repo, instead of here. This ensures that the server can tell the difference between a response and a request. The old method (resp == nil) didn't work because we use interfaces here, and the interfaces would often have types, but not values.	2016-10-28 16:46:40 -07:00
Quinn Slack	c04eec1600	initial commit	2016-10-11 15:56:18 +02:00