[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18564 [Tor]: Improve our client HS descriptor fetch logic
#18564: Improve our client HS descriptor fetch logic
---------------------+------------------------------------
Reporter: dgoulet | Owner:
Type: defect | Status: new
Priority: Medium | Milestone: Tor: 0.2.9.x-final
Component: Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-hs | Actual Points:
Parent ID: | Points: medium
Reviewer: | Sponsor: SponsorR-can
---------------------+------------------------------------
Comment (by arma):
I think we should do the same fetch behavior regardless of how much client
requests are pending.
The simple answer then is to do one fetch and wait for it to succeed or
fail.
If we want to get fancy, we could launch a few in parallel, and close down
the others once one succeeds. (Benefit: you get your answer more reliably
and probably a bit more quickly. Drawback: you load down the network more,
and also you expose your interest in the onion service to more relays.)
But it seems crazy to me to have more outstanding fetches as we have more
pending client requests.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18564#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs