-
Notifications
You must be signed in to change notification settings - Fork 279
Move lightning-block-sync's HTTP logic into here #166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Note that there are still uses of |
Hmm, right, would need a macro to cover those, too, though if you took the std option and stripped them it should all work, just need to macro-ize it. |
I wonder if it shouldn't be a common problem for API client packages that want to support both async and sync calls.. I might still have a branch where I tried to implement batching with potential async support in mind by having every API method return some kind of Unless there is another common way to solve this problem in the ecosystem, I might give that a try. |
Seems like a reasonable approach, though it may take a little thought on how to refactor |
Adapts other actors to fit the Carrier in. Temporarily uses both rust-lightnings rpc and bitcoincore-rpc rpc clients. Waiting for both to be merged. Related to: rust-bitcoin/rust-bitcoincore-rpc#166
Please give some feedback on this idea I have, it might be relevant to this discussion: #212 |
Because we also support Bitcoin Core REST and potentially nginx/Cloudflare-proxied REST, we ended up with our own one-dependency HTTP client in rust-lightning. We currently use it with our own JSON parsing, though switching to this crate instead may be nice. In order to do that, we'd need to move the HTTP bits to here (they support async, but without the tokio feature, the "async" keyword on the functions is unused, just need a macro to figure out how to insert-or-not an async keyword), maybe in its own subcrate.
The current HTTP/RPC/REST client stuff is at https://github.com/rust-bitcoin/rust-lightning/tree/main/lightning-block-sync/src
The text was updated successfully, but these errors were encountered: