DanGould / rust-payjoin / 39767406840

88%

master: 87%

push

github

Return the key fetch order as plain data

fetch_ohttp_keys_with took the caller's HTTP fetch as a closure and
drove the loop itself, and the FFI wrapped that in an OhttpKeysFetcher
foreign trait, a result record and two error types. A binding app that
routes its traffic through Tor or a proxy had to adapt its client to
that trait to keep the key fetch on the same path as its posts.

RequestHandler::key_fetch_order returns the relay and directory pairs
to try, each directory over every relay that is not itself before the
next directory. The caller tries them in order with its own client and
pins the first directory that returns keys. Because the pairs are
grouped by directory, a caller that can tell a failure is the
directory's skips to the next directory, and one that can't retries
the directory over its other relays. The library loop could only do
the latter.

payjoin-cli loops over the order with payjoin::io. It can't yet tell
directory errors from relay errors, so it tries every pair. The FFI
exports key_fetch_order and a KeyFetch record, and drops the fetcher
trait, FetchedOhttpKeys, DirectoryFetchError and RequestHandlerError.

30 of 41 new or added lines in 2 files covered. (73.17%)

15760 of 17984 relevant lines covered (87.63%)

327.2 hits per line