#jsonrpc #macro #http #client

jsonrpc_client

An async, macro-driven JSON-RPC client with pluggable backends

9 releases (breaking)

0.7.1 Aug 26, 2021
0.7.0 Jul 28, 2021
0.6.0 Apr 26, 2021
0.5.1 Feb 22, 2021
0.2.0 Oct 12, 2018

#34 in HTTP client

Download history 262/week @ 2021-05-30 387/week @ 2021-06-06 412/week @ 2021-06-13 812/week @ 2021-06-20 528/week @ 2021-06-27 906/week @ 2021-07-04 770/week @ 2021-07-11 397/week @ 2021-07-18 198/week @ 2021-07-25 139/week @ 2021-08-01 208/week @ 2021-08-08 680/week @ 2021-08-15 394/week @ 2021-08-22 1118/week @ 2021-08-29 742/week @ 2021-09-05 685/week @ 2021-09-12

1,958 downloads per month
Used in bitcoin_rpc_client

MIT/Apache

27KB
545 lines

No bullshit JSON-RPC client for Rust

Features

  • No boilerplate: Driven by proc-macros
  • No client lock-in: Complete freedom over underlying HTTP client
  • Lightweight: Only depends on syn and serde
  • Async-ready

How does it work?

We take a trait as input to a proc-macro and output another one that has default implementations for all the functions. This allows us to take away all the boilerplate of making JSON-RPC calls and you get to define a nice interface at the same time!

How do I use it?

  1. Depend on jsonrpc_client:

    [dependencies]
    jsonrpc_client = { version = "*", features = ["reqwest"] }
    
  2. Define a trait that describes the JSON-RPC API you want to talk to and annotate it with #[jsonrpc_client::api]:

    #[jsonrpc_client::api]
    pub trait Math {
        async fn subtract(&self, subtrahend: i64, minuend: i64) -> i64;
    }
    
  3. Define your client:

    #[jsonrpc_client::implement(Math)]
    struct Client {
        inner: reqwest::Client,
        base_url: reqwest::Url,
    }
    
  4. Start using your client!

Backends

Currently, the client supports several backends, all of them can be activated via a separate feature-flag:

  • reqwest
  • surf
  • isahc

Support for more backends is welcomed.

Unfortunately, not all can be supported. In particular:

  • hreq: Cannot be supported because their Agent takes &mut self for sending a request which doesn't work with the SendRequest trait.
  • awc: Cannot be supported because their Client does not implement Send.

Dependencies

~2.3–9MB
~203K SLoC