Ok Thomas, I understood, it wasn't intention do like that. The xspf file associated to each station is instead real-time updated? Why not all the stations has got that file? Why stations like http://212.162.68.230/1.mp3 and others are not inside yp.xml? PS I'm sorry but my mail client automatically answers to the sender! 2012/9/25 R?cker Thomas <thomas.ruecker at tieto.com>> Hi, > > On 25/09/12 15:46, renato fringuello wrote: > > Can you tell me how often is yp.xml updated? > > > > Currently the XML is updated roughly every 10 minutes. (which could > change at any time really) > Please notice though that polling every 10 minutes is NOT OK! > I see some incredibly inefficient software being responsible for the > majority of the load on the server. (Think thousands of users and > multiple requests per client - adds up to a LOT.) > > So please be sensible. Don't auto-update the list constantly - it > doesn't change much anyway. > e.g. reload only if the user requests an update. > > If you have further questions, don't hesitate to ask. > > Cheers > > Thomas > > > 2012/9/25 R?cker Thomas <thomas.ruecker at tieto.com > > <mailto:thomas.ruecker at tieto.com>> > > > > Hi Renato, > > > > please subscribe to the mailing lists, so that you don't miss > > answers. (Also please don't send HTML mail) > > > > > > On 24/09/12 17:14, renato fringuello wrote: > > > > Hi, my name is renato and I'm trying to develope a player for > > Icecast screams, how can I get some help? > > > > > > This mailing list is the right place for development related > > discussion. > > There is also the #icecast IRC channel on freenode. > > > > > > > > I need to obtain all italian streams. > > > > > > As of right now this is your best bet: > > http://dir.xiph.org/yp.xml > > Note: you really should implement support for compression > > according to RFC2616. > > It makes about a 10x difference in transferred data. > > > > Cheers > > > > Thomas > > > > > > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast-dev/attachments/20120925/d8f0f1f3/attachment-0001.htm
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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast-dev/attachments/20120925/7219cb78/attachment.htm
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
>