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

Re: [tor-bugs] #12869 [Onionoo]: protocol api separation

#12869: protocol api separation
-------------------------+----------------------
     Reporter:  iwakeh   |      Owner:  iwakeh
         Type:  task     |     Status:  assigned
     Priority:  normal   |  Milestone:
    Component:  Onionoo  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+----------------------

Comment (by karsten):

 Regarding development guidelines: these guidelines were the result of a
 discussion between sysadmins and developers about two months ago.  What
 you see on that wiki page is the compromise we came up with.  I'm aware
 that Debian packages are sometimes old, but they should at least see all
 security updates.  This is not perfect for software development, but it's
 what keeps sysadmins happy.  And who doesn't want happy sysadmins?

 Regarding an interface API: I agree that there's not a huge market yet for
 a Java library for Onionoo, but that could be a chicken-and-egg problem.
 Let's provide one.  But interfaces alone are not sufficient, we'll also
 need implementing classes, and we may want to provide some download and
 caching logic.  How about we create a package
 `org.torproject.onionoo.client` with the API that a Java Onionoo client
 would need?  That package would depend on the docs package and maybe
 others.  We could provide an Ant target to produce a jar with just the
 interfaces and classes that a Java Onionoo client needs.  Does that make
 sense?  Want to design such an API package?

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