Closed kke closed 6 years ago
Might have been a waste of time. The public endpoints are working and responding 4x faster, but the signed ones do not, perhaps binance can't read the api key header or then I'm just sending it wrong.
I suppose reusing connections on http1 can bring the same kind of speed boost. Need to try.
I will take the commits you pushed to this PR and try to work with them in 1.0.
Still quite untested and mostly proof of concept / work in progress.
Adds net-http2 dependency and brings an alternative
Binance::Client::REST::HTTP2
client for you to play with.This can be used like:
or in not-so-async manner:
I haven't done any real benchmarking, but it SEEMS to react quite a lot faster than the regular
Binance::Client::REST
does (especially after the first request)