[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18910 [Metrics/CollecTor]: distributing descriptors accross CollecTor instances
#18910: distributing descriptors accross CollecTor instances
-------------------------------+-----------------------------------
Reporter: iwakeh | Owner: iwakeh
Type: enhancement | Status: needs_information
Priority: Medium | Milestone:
Component: Metrics/CollecTor | Version:
Severity: Normal | Resolution:
Keywords: ctip | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------+-----------------------------------
Changes (by iwakeh):
* status: assigned => needs_information
Comment:
I agree, the protocol option is too much implementation effort. The
protocol design could be made simple by copying the existing protocol, but
implementation of this protocol and having a service up and running all
the time answering requests is a lot work and not really necessary.
Regarding you're suggestion for the download-option from 'recent' I'm
wondering if this could be designed a little more fine grained, in order
to save a bit bandwidth, processing time, and memory?
Usually there are only a few descriptors missing and it is easy to
determine which document to download. For votes and consensus the download
url can be constructed directly and for the referenced descriptors it is
possible to infer (using a directory listing from the remote collector
instance, e.g. <other instance>/recent/relay-descriptors/extra-infos/)
which doc respective url should provide the missing information.
Would that be a feasible approach?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18910#comment:3>
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