[tor-bugs] #4439 [Metrics Utilities]: Develop a Java/Python API that wraps relay descriptor sources and provides unified access to them

[Tor Bug Tracker & Wiki]

#4439: Develop a Java/Python API that wraps relay descriptor sources and provides
unified access to them
-------------------------------+--------------------------------------------
 Reporter:  karsten            |          Owner:  karsten
     Type:  task               |         Status:  new    
 Priority:  normal             |      Milestone:         
Component:  Metrics Utilities  |        Version:         
 Keywords:                     |         Parent:         
   Points:                     |   Actualpoints:         
-------------------------------+--------------------------------------------

Comment(by atagar):

 > Not tangential. I think that's pretty much what the API should do.
 > By metrics service you mean the metrics database?

 ... yikes. I just realized that I had *completely* misunderstood what
 you're proposing. Probably for the better though since this sounds related
 to functionality I was already planning to write.

 Stem will need functions and tests for parsing
 consensus/descriptor/microdescriptor data into developer friendly objects.
 This was going to be abstracted into a general Relay class that lazy loads
 ns/desc information as needed (with a method for triggering eager loads).
 I'd be more than happy to write functions and integ tests to alternatively
 fetch them from the cache or authorities/mirrors. However, this work would
 be a month or two out for me (still busy with shoring up the utils and
 testing).

 Completely ignore the rest of my last comment - for some reason I'd
 assumed that this would be a service API for querying the metrics db
 externally.

 Cheers! -Damian

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4439#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online