Question: url vs url_resolved

[boyska]

This is more of a question than a real bug, so sorry for "abusing" the issue tracker for this.

Let's look at this: http://all.api.radio-browser.info/json/stations/byuuid/12cfc0d8-0ff1-4dcb-9c63-1f8f46538dc9

The field url is different than url_resolved. In fact, it's the kind of setup where every listener will be redirected to the first available server.
I'd like RadioDroid (and actually, every similar app) to listen to url and to never use url_resolved on its own. In fact, the specific server names can change over time, they can go down for maintainance, technical issues, etc.

Is this the case? Do you have any idea of what other applications do? What's the point for url_resolved?

[segler-alex]

url_resolved gets updated automatically by starting with "url" and GETting (http request) until the real stream url is found. this url is then saved as "url_resolved". it does also open playlist files (e.g.: m3u, pls, xspf,...)
This is needed for clients who cannot do some/all of this steps on their own, like browsers. it makes it easier to just play the url. like i said, it gets updated daily automatically

[boyska]

Thanks, I now understand better how it works and its purpose. Do you have any pointer as to where is the code that does that? I'd like to improve the logic behind following redirects, but I'm not sure I'm finding it. I know this is the issue tracker of an application, and not of the database, but I also know that you are involved with both, so... thank you for your patience :)