For example, this station: http://radio.dyne.org:8000/ondarossa.mp3
has got a xspf file?
I obtain a message: Could not parse XSLT file when i try to open it
For the stations that I can't found in yp.xml
(e.g. http://212.162.68.230/1.mp3
http://212.162.68.230/2.mp3
http://212.162.68.230/3.mp3
http://stream15.top-ix.org/ondequadre )
it means they aren't on an official database ? because I can hear
them! so they exist!
The project to enrich the APIs is a long term plan? Because I think
this is a very good project and it needs APIs!!
Thanks again for your disponibility and sorry for my english!
2012/9/25 R?cker Thomas <thomas.ruecker at
tieto.com>:> On 25/09/12 16:42, renato fringuello wrote:
>
> Ok Thomas, I understood, it wasn't intention do like that.
> The xspf file associated to each station is instead real-time updated?
>
>
> The XSPF files are generated on the fly, yes.
> Beware they are NOT intended for automatic processing. They are for users
to
> browse and click.
> Also the URLs for those XSPF files are NOT stable and may change at any
time
> depending on what happens in the database.
> The whole web-interface should NOT be considered an API. We might change it
> without notice.
>
> The only 'API' right now is the XML file. (We do plan to provide a
more rich
> API, but that's still in the planning stage)
>
>
>
> Why not all the stations has got that file?
>
>
> I briefly glanced at the website and don't see any stations that
don't have
> a XSPF link next to them.
> Care to provide a link to a dir.xiph.org page where XSPF is missing so I
can
> investigate the problem?
>
>
>
> Why stations like http://212.162.68.230/1.mp3 and others are not inside
> yp.xml?
>
>
> I have manually queried the SQL database and do not see such a stream in
the
> database at all.
> Notice that
> a) your web-browser might have cached a station that is no longer streaming
> and thus got delisted
> b) the station might have appeared/disappeared during the last 10 minutes
> and thus there might be a difference
> c) ...
>
> Hope that helps
>
> Thomas
>
> _______________________________________________
> Icecast-dev mailing list
> Icecast-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast-dev
>
On 25/09/12 18:41, renato fringuello wrote:> For example, this station: http://radio.dyne.org:8000/ondarossa.mp3 > has got a xspf file? > I obtain a message: Could not parse XSLT file when i try to open itAh, you are talking about the /individual/ servers, not about http://dir.xiph.org - that explains it! So let's deconstruct this: This is the status page: http://radio.dyne.org:8000/ It has a link to http://radio.dyne.org:8000/blackout.mp3.xspf If you click that link it will show "Could not parse XSLT file". This is a problem of /this/ particular server. I think in Icecast 2.3.x there was a problem that the make-file would not install the xspf.xsl file properly and thus some distributions carried 'broken' packages. Sadly nothing you can do about that on your side. Most up to date servers should provide that though. (the administrator can disable it though, together with the web interface).> For the stations that I can't found in yp.xml > (e.g. http://212.162.68.230/1.mp3 > http://212.162.68.230/2.mp3 > http://212.162.68.230/3.mp3 > http://stream15.top-ix.org/ondequadre ) > it means they aren't on an official database ? because I can hear > them! so they exist!While those stations do exist they did not chose to be listed on dir.xiph.org. It is up to the server administrator and the stream themselves to enable directory listing. Not everyone does that. c.f. http://www.icecast.org/docs/icecast-2.3.3/icecast2_config_file.html#yp http://www.icecast.org/docs/icecast-2.3.3/icecast2_config_file.html#mount> The project to enrich the APIs is a long term plan? Because I think > this is a very good project and it needs APIs!!Yes it's a long term plan. First I'd like to understand the needs of application developers. Likely it's going to be quite simple though so that we can cope with the load of many clients on the server side.> Thanks again for your disponibility and sorry for my english!No problem, we're here to help. Cheers Thomas
Ok, you have been very clear. If I have any other questions I will contact again. Thanks a lot. Best Renato 2012/9/25 R?cker Thomas <thomas.ruecker at tieto.com>:> On 25/09/12 18:41, renato fringuello wrote: >> For example, this station: http://radio.dyne.org:8000/ondarossa.mp3 >> has got a xspf file? >> I obtain a message: Could not parse XSLT file when i try to open it > Ah, you are talking about the /individual/ servers, not about > http://dir.xiph.org - that explains it! > > So let's deconstruct this: > This is the status page: http://radio.dyne.org:8000/ > It has a link to http://radio.dyne.org:8000/blackout.mp3.xspf > If you click that link it will show "Could not parse XSLT file". > This is a problem of /this/ particular server. > > I think in Icecast 2.3.x there was a problem that the make-file would > not install the xspf.xsl file properly and thus some distributions > carried 'broken' packages. > Sadly nothing you can do about that on your side. Most up to date > servers should provide that though. (the administrator can disable it > though, together with the web interface). > > >> For the stations that I can't found in yp.xml >> (e.g. http://212.162.68.230/1.mp3 >> http://212.162.68.230/2.mp3 >> http://212.162.68.230/3.mp3 >> http://stream15.top-ix.org/ondequadre ) >> it means they aren't on an official database ? because I can hear >> them! so they exist! > > While those stations do exist they did not chose to be listed on > dir.xiph.org. > It is up to the server administrator and the stream themselves to enable > directory listing. Not everyone does that. > c.f. http://www.icecast.org/docs/icecast-2.3.3/icecast2_config_file.html#yp > http://www.icecast.org/docs/icecast-2.3.3/icecast2_config_file.html#mount > > >> The project to enrich the APIs is a long term plan? Because I think >> this is a very good project and it needs APIs!! > > Yes it's a long term plan. First I'd like to understand the needs of > application developers. > Likely it's going to be quite simple though so that we can cope with the > load of many clients on the server side. > > >> Thanks again for your disponibility and sorry for my english! > > No problem, we're here to help. > > Cheers > > Thomas > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev