[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #28667 [Core Tor/sbws]: Obtain the new descriptors and network status documents by signals instead of every 5min

#28667: Obtain the new descriptors and network status documents by signals instead
of every 5min
-------------------------------------------------+-------------------------
 Reporter:  juga                                 |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:  sbws:
                                                 |  unspecified
Component:  Core Tor/sbws                        |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tech-debt, refactor, scanner,        |  Actual Points:
  relays                                         |
Parent ID:  #30733                               |         Points:  1
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Description changed by teor:

Old description:

> The network status and descriptors are obtained every 5min
> https://gitweb.torproject.org/sbws.git/tree/sbws/lib/relaylist.py#n144.
> Is there any reason for that?.
> I think torflow obtain them as they come.
> It could be done with steam using:
> {{{
> controller.add_event_listener(
>             listener_fn, EventType.NS, EventType.NEWDESC)
> }}}
> Also, instead overwriting those values, Relay could have a dictionary
> (key would be the timestamp) with a subset of the attributes of document,
> in case we might need to calculate median/mean of those attributes

New description:

 The network status and descriptors are obtained every 5min
 https://gitweb.torproject.org/sbws.git/tree/sbws/lib/relaylist.py#n144.
 Is there any reason for that?.
 I think torflow obtain them as they come.
 It could be done with stem using:
 {{{
 controller.add_event_listener(
             listener_fn, EventType.NS, EventType.NEWDESC)
 }}}
 Also, instead overwriting those values, Relay could have a dictionary (key
 would be the timestamp) with a subset of the attributes of document, in
 case we might need to calculate median/mean of those attributes

 Edit: fix typo

--

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28667#comment:7>
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