Move to APIv3

[dbrgn]

http://8tracks.com/developers/api_v3

[octogene]

In the new api a search doesn't return the duration, track_counts nor user login for the mix. Thus, we would need to make a request with get_mix_with_id for each mix showed in search results. I've made some initial tests (apiv3 branch) and it considerably slows down the displaying of results. I'm not quite sure how we could manage this problem, maybe by caching all the mixes info before displaying them but i suppose it will also slows down the search process since we'll need to make n requests for n results per page.

[dbrgn]

Oh, that's inconvenient... Maybe you could send the guys from 8tracks a feature request?

I guess the v2 API will be maintained for quite some time, so there's no need to rush.

[octogene]

I've found how to do it without having to make a request for each mix after looking at http://8tracks.com/developers/includes. I was just requesting the wrong field, we must request mixes_detail instead of mixes. I've made the changes in my branch.

[dbrgn]

OK, great. Please create a pull request when you think it's stable :)