{"action":"opened","issue":{"url":"https://api.github.com/repos/steemit/steem/issues/216","repository_url":"https://api.github.com/repos/steemit/steem","labels_url":"https://api.github.com/repos/steemit/steem/issues/216/labels{/name}","comments_url":"https://api.github.com/repos/steemit/steem/issues/216/comments","events_url":"https://api.github.com/repos/steemit/steem/issues/216/events","html_url":"https://github.com/steemit/steem/issues/216","id":167931295,"number":216,"title":"Allow string ID for JSONRPC messages","user":{"login":"theoreticalbts","id":10215982,"avatar_url":"https://avatars.githubusercontent.com/u/10215982?v=3","gravatar_id":"","url":"https://api.github.com/users/theoreticalbts","html_url":"https://github.com/theoreticalbts","followers_url":"https://api.github.com/users/theoreticalbts/followers","following_url":"https://api.github.com/users/theoreticalbts/following{/other_user}","gists_url":"https://api.github.com/users/theoreticalbts/gists{/gist_id}","starred_url":"https://api.github.com/users/theoreticalbts/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theoreticalbts/subscriptions","organizations_url":"https://api.github.com/users/theoreticalbts/orgs","repos_url":"https://api.github.com/users/theoreticalbts/repos","events_url":"https://api.github.com/users/theoreticalbts/events{/privacy}","received_events_url":"https://api.github.com/users/theoreticalbts/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-27T19:06:18Z","updated_at":"2016-07-27T19:06:18Z","closed_at":null,"body":"\r\nContinuing discussion of the second issue raised in #213:  Namely, FC's JSON-RPC implementation is not spec-compliant as it doesn't allow string ID's.\r\n\r\nI think the problem is [here](https://github.com/steemit/fc/blob/c672e3b4b4676ee90a63dbee4179207bbcd14e56/src/rpc/json_connection.cpp#L150-L151) -- basically we do internal bookkeeping with `_awaiting` which is declared as a `map` using `uint64_t` as its key.  I'm not sure `variant` (the FC type representing a JSON object) has the right interface to be used as a key in a map, and I'm sure that changing it to anything other than a uint64 will have negative performance implications.\r\n\r\nI'm tempted to tag this wontfix, but we should strive to be spec-compliant."}}
{"actor":{"display_login":"theoreticalbts"}}