Request id is hardcoded in the http(s) client about jsonrpc2-elixir

[ericentin]

I'm not sure I understand what issue this is causing? AFAIK the purpose of the request id is when you are multiplexing multiple requests over a single connection, in order to identify which request a response corresponds to.

[nkmanolovsumup]

Yes, the ID is used for multiplexing (and primarily so), however, it's purpose is not defined in the specification as such. I agree that for single http calls it doesn't make too much sense, however, the library assumes that the client doesn't need to pass a custom id. It would be nice to be able optionally pass it.

[ericentin]

The purpose is defined in the spec, as far as I can tell:

The Server MUST reply with the same value in the Response object if included. This member is used to correlate the context between the two objects.

If you want to add a PR to add an optional argument to change the request ID from 0 to another value, I would welcome it, but it will also have to validate that the passed value is a valid request ID.

[whitered]

+1 here. I'm experiencing issues with hardcoded id too, the problem is tendermint rpc server doesn't accept integer id value (yes, it's Tendermint's fault but still my problem). I'm going to change the default id to "0" (string), any chance this change can be merged in the lib?

[ericentin]

Resolved, released soon