Fails to return null about json-rpc HOT 5 CLOSED

@solorab , let me take a look.

There is a question: Why do you need this method? Could you provide use case? May be it is possible to use json-rpc notification for that.

from json-rpc.

I want to support putting ids to requests to call methods written to listen notification.
When I write a function for notification and a client sends a request with id, I want to return a valid response to the request. I don't like to return nothing to client (forbidden by the specification) nor add a line to return a dummy result explicitly.

from json-rpc.

I see. If you send id within request, current implementation does not support None response. As I get you right, you need to notify server from the client side (to call methods written to listen notification).
If you omit ids for request (either explicitly from client, or via passing is_notification=True to Request constructor) then you send notification. Notification does not require any response from dispatcher function, so, you could use "return None".
If notification function is executed correctly, server sends 200 Response, if there are exceptions raised during notification, response would have error in the body. Basically, if something returned, then there are errors.

@solorab, does it work for you?

from json-rpc.

I am writing an application which works with plugins through TCP. So It cannot return returncodes and I want to accept requests widely.
Please excuse me adding information later.

from json-rpc.

Information was not added to the issue, closed as outdated.

from json-rpc.