Re: [tor-bugs] #6682 [Compass]: merge atlas and compass?

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#6682: merge atlas and compass?
-------------------------+--------------------------------------------------
 Reporter:  cypherpunks  |          Owner:                   
     Type:  enhancement  |         Status:  needs_information
 Priority:  minor        |      Milestone:                   
Component:  Compass      |        Version:                   
 Keywords:               |         Parent:                   
   Points:               |   Actualpoints:                   
-------------------------+--------------------------------------------------

Comment(by cwacek):

 Replying to [comment:8 gsathya]:
 > Replying to [comment:7 karsten]:
 > >
 > > I like the idea of moving the Compass functionality to the back-end.
 But two back-end services with Onionoo and Compass doesn't make much
 sense.  Everything that Compass knows is already known to Onionoo.  This
 functionality should then be added to Onionoo.
 >
 > But Compass and Onionoo do different things. I don't know if any other
 application is going to use the data that Compass requires. I guess
 maintaining two different backend services are going to be a pain, so yes
 we should probably merge the two.
 >
 > > Can you describe the interface that you have in mind?  What queries
 would the extended Atlas send to the extended Onionoo?  Maybe I can help
 integrating those queries into Onionoo's current interface.
 >
 > I think pretty much what compass.py does. I will think more about a more
 optimized interface such that we can offload some kind of processing work
 to the client side js.

 This doesn't solve the discussion, but I should mention that my rewrite of
 compass.py already makes it spit out JSON rather than text strings, so
 that might be a little bit less work if you wanted to turn it into a
 service. When you run it from the command line it looks like what
 compass.py used to do, but that's just because of the print_selection call
 at the end.  For example, loading
 compass.torproject.org/result.json?exit_filter=all_relays&links&sort=cw&sort_reverse&country=&ases=AS3320
 directly will just give you the JSON.

 The client side JS is currently handling all of the display and input, but
 isn't actually doing any processing.

 >
 > >
 > > I don't know of any plans to rewrite Atlas, and I don't see how we
 have the developer resources to do that.  Can you be more specific why
 it's hard to extend Atlas to support Compass' front-end functionality,
 assuming that Onionoo would support Compass' back-end functionality?
 >
 > I haven't really looked at the Atlas code, but I don't suspect it's
 going to be impossible to do this. We should also figure out how to make
 this intuitive for people to use so that they don't get confused.
 >
 > > I agree that this is a pretty big task.  But that shouldn't us from
 making plans.
 >
 > +1

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