[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9778 [Onionoo]: Adding votes documents to Onionoo
#9778: Adding votes documents to Onionoo
-----------------------------+---------------------
Reporter: karsten | Owner: karsten
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Onionoo | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-----------------------------+---------------------
Comment (by wfn):
Karsten:
> wfn: I think it makes sense to add these documents to good-old-Java-
Onionoo, so that there's just one more document type that your shiny-new-
Python-Onionoo can treat like summary, details, bandwidth, and weights
documents. Does that work for you?
Introducing a completely separate document type / API point for votes
makes sense to me. As we briefly discussed on IRC, I'd be curious to maybe
try and eventually implement this new votes document in the new python-
onionoo / torsearch itself. But for now, I'll assume that the new votes
document should be treated like the Onionoo weights and bandwidth
documents (i.e., "outsourced" to the java-onionoo proper.)
I think Roger hinted at the idea that it might be useful to be able to
query Onionoo/whatever for vote info on past consensuses as well, to be
able to compare things, etc. It would indeed (as Karsten said) be probably
a very DB-expensive (and disk i/o-bound) operation / API point; but if
there's interest, I could try later on looking at possible solutions (as I
said, Redis and/or PostgresSQL's 'hstore' might be the proper tool(s) for
the job.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9778#comment:1>
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