by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Lev Orekhov
    @lorehov
    Hello!
    Kirill Pavlov
    @pavlov99
    @lorehov , it works!
    Lev Orekhov
    @lorehov
    @pavlov99 , yeah it works, but I kinda slowpoke and already solve a problem :) so thanks for your feedback.
    randomhooman
    @randomhooman19_twitter
    Is there a way to find an existing identity of a user using json rpc shh?
    Ivan
    @biozz
    Hi, I would like to know if subdomains are possible with flask backend? i.e. making requests through api.example.com. I tried registering blueprint with subdomain, but it seems jsonrpc() in flask backend doesn't have additional argument for that
    Pureewat Kaewpoy
    @sgnsys3
    Hello, Can you help me about How to access id of JSON-RPC ?
    Ivan
    @biozz

    @sgnsys3 Hi, json-rpc requests are plain json payloads with some rules on top, so basically you just parse the body of the request and get the id.

    For example, if you use Flask backend, you can access flask’s request.data, it will be json encoded. Or even easier request.json[‘id’] - will give you the id...

    @api.dispatcher.add_method
    def echo(kwargs):
        print(request.data)  # b'{"method": "echo", "params": ["echome!"], "jsonrpc": "2.0", "id": 0}'
        return kwargs
    Pureewat Kaewpoy
    @sgnsys3
    @biozz Thank you for suggestion.
    inaltoasinistra
    @inaltoasinistra

    hello folks, I'd like to implement a json-rpc v1.0 server but I think I found a problem with the protocol specification.
    I installed version 1.13.0 from pip.
    In the responses of version 1.0 both 'result' and 'error' entries must be defined, and must be null if not used. But only the used attribute is defined.

    For example, this is my call

    {'method': 'sum_all', 'id': 'curltest', 'params': (0, 1.1, 345, 1e-06)}

    end this is the response

    {'id': 'curltest', 'result': 346.100001}

    inaltoasinistra
    @inaltoasinistra
    I opened as issue
    pavlov99/json-rpc#113
    bye