[tor-bugs] #17741 [GetTor]: GetTor RESTful API

[Tor Bug Tracker & Wiki]

#17741: GetTor RESTful API
--------------------+------------------------------
 Reporter:  ilv     |          Owner:  ilv
     Type:  task    |         Status:  needs_review
 Priority:  Medium  |      Milestone:
Component:  GetTor  |        Version:
 Severity:  Normal  |     Resolution:
 Keywords:          |  Actual Points:
Parent ID:          |         Points:
  Sponsor:          |
--------------------+------------------------------
Changes (by ilv):

 * status:  new => needs_review


Comment:

 Ok, I've pushed a
 [https://gitweb.torproject.org/gettor.git/commit/?h=develop&id=6b12e964082feb9ffc1d5b7da84ead87378b8ae9
 first version of the RESTful API] to the develop branch. So far I have
 tested it on my computer, so I'm attaching the json results for each
 resource as follows:

 `/` => resources.json
 `/providers` => providers.json
 `/providers/github` => providers-github.json
 `/providers/github?os=windows` => providers-github-filter-os.json
 `/providers/github?os=windows&lc=zh` => providers-github-filter-os-lc.json
 `/latest` => latest.json
 `/latest/stable` => latest-stable.json
 `/latest/stable?os=linux` => latest-stable-filter-os.json
 `/latest/stable?os=linux&lc=fa` => latest-stable-filter-os-lc.json
 `/mirrors` => mirrors.json

 Instead of using `/{provider}/links` to display links according to a
 specific provider, I used `/providers/{provider}`. Also, I used OS and LC
 as filter for both providers links and latest version links.

 **Important note**: in the end I decided to go with flask and flask-
 restful, it turned out to be easier and I had some experience with it in
 the past. Also, a quick search on the internet shows that it is way more
 popular than cyclone for making RESTful APIs.

 Looking forward to your comments!

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