<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18702">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Based on icecast 2.3.2 (openbsd 4.5
package)</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Inactive Mount-Point display:</FONT></DIV>
<DIV><FONT size=2 face=Arial><mount>'s that have a fallback defined and
have currently no source, will appear in status.xsl, after a signal HUP (kill -s
1) while the fallback-mount is active (could also be a mp3 file). This
could also happen by properly killing icecast and restarting, and where the
source (ices in my case) is reconnectin quite instantly.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Remedy: disconnect the fallback-source, do the
signal HUP, reconnect the fallback-source.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Idea: Don't display any inactive mounts in
status.xsl in any case.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Slave with <master-server>
defined:</FONT></DIV>
<DIV><FONT size=2 face=Arial>In case the master has a fallback (hidden) for
a specific mount, listeners on the slave will get the master's fallback for a
few seconds only, after the source is gone, and then disconnects from the
slave.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Remedy: set a <mount> with the same name with
fallback on the slave. Slave will then serve the fallback.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Idea: Let listeners connecting to the
slave get the master's fallback stream, like they would connect directly to
the master.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Slave with <relay> defined:</FONT></DIV>
<DIV><FONT size=2 face=Arial>The master's fallback is working here. However,
when the first listener gets the fallback (with its metadata and no-yp), and the
source is taking over, metadata are not coming, and yp not
updating.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Idea: The slave should recognize the take-over from
fallback to actual source and vice-versa.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>When a fallback occurs (source is disconnecting),
the mount disappears from the master's status.xsl, but not from the slave's when
listeners are connected to.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Idea: Make it disappear on the slave, while
listeners are still able to get the master's fallback stream.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>In case on-demand on, the mount appears in
status.xsl after the first listeners connects. When there is no more listener on
the slave, the mount remains on status.xsl without server name, and description,
but with Listeners: 0 etc.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>In case on-demand off, and the mount inactive (no
source), i doesn't show up in status.xsl, but when a listeners can connect and
gets the master's fallback, the mound will appear in status.xsl.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Idea: That shouldn't happen. When a listeners gets
the fallback on the master directly, the desired mount they wanted to reach
doesn't show up.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>On-demand:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>For my taste and logic, on-demand shall only be
applicable to the streams themselves.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Mount-Point information and Metadata shall always
be transmitted periodically (option) and displayed for both
<master-server> and <relay>,</FONT></DIV>
<DIV><FONT size=2 face=Arial>and only when the mounts are active.</FONT></DIV>
<DIV><FONT size=2 face=Arial>When mounts are inactive, they must never be
displayed.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Trying to get listen to an inactive mount, the
slave shall always knock to the master, and at least get the fallback if there
is one.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Lorenzo Pirovano (aka mankind_ @ #icecast @
freenode)</FONT></DIV></BODY></HTML>