[xiph-cvs] cvs commit: icecast/doc icecast2_relay.html icecast2_yp.html

[Manuel Lora]

vanguardist    03/11/18 12:43:05

  Modified:    doc      icecast2_relay.html icecast2_yp.html
  Log:
  going and going...

Revision  Changes    Path
1.2       +2 -2      icecast/doc/icecast2_relay.html

Index: icecast2_relay.html
===================================================================
RCS file: /usr/local/cvsroot/icecast/doc/icecast2_relay.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- icecast2_relay.html	13 Nov 2003 03:50:30 -0000	1.1
+++ icecast2_relay.html	18 Nov 2003 17:43:05 -0000	1.2
@@ -11,12 +11,12 @@
 <br>
 <br>
 <h2>Type of Relays</h2>
-<p>There are two types of relays that icecast supports.  The first type is when both master and slave servers are icecast2 servers.  In this case, a "master-slave" relay can be setup such that all that needs to be done is configure the slave server with the connection information (serverip:port) of the master server and the slave will mirror all mountpoints on the master server.  The slave will also periodically check the master server to see if any new mountpoints have attached and if so, then will relay those as well.  The second type of relay is a "single-broadcast" relay.  In this case, the slave server is configured with a serverip+port+mount and only the mountpoint specified is relayed.  In order to relay a broadcast stream on a Shoutcast server, you must use the "single-broadcast" relay and specify a mountpoint of "/".</p>
+<p>There are two types of relays that icecast supports.  The first type is when both master and slave servers are icecast2 servers.  In this case, a "master-slave" relay can be setup such that all that needs to be done is configure the slave server with the connection information (serverip:port) of the master server and the slave will mirror all mountpoints on the master server.  The slave will also periodically check the master server to see if any new mountpoints have attached and if so will relay those as well.  The second type of relay is a "single-broadcast" relay.  In this case, the slave server is configured with a serverip+port+mount and only the mountpoint specified is relayed.  In order to relay a broadcast stream on a Shoutcast server, you must use the "single-broadcast" relay and specify a mountpoint of "/".</p>
 <br>
 <br>
 <br>
 <h2>Setting Up A Master-Slave Relay</h2>
-<p>In order to setup a relay of this type, both servers (the one you wish to relay and the one doing the relaying) need to be icecast2 servers. The following configuration snippet is used as an example:</p>
+<p>In order to setup a relay of this type both servers (the one you wish to relay and the one doing the relaying) need to be icecast2 servers. The following configuration snippet is used as an example:</p>
 <pre>
     &lt;master-server&gt;192.168.1.11&lt;/master-server&gt;
     &lt;master-server-port&gt;8001&lt;/master-server-port&gt;

<p><p>1.2       +3 -3      icecast/doc/icecast2_yp.html

Index: icecast2_yp.html
===================================================================
RCS file: /usr/local/cvsroot/icecast/doc/icecast2_yp.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- icecast2_yp.html	13 Nov 2003 03:50:30 -0000	1.1
+++ icecast2_yp.html	18 Nov 2003 17:43:05 -0000	1.2
@@ -12,9 +12,9 @@
 <br>
 <br>
 <br>
-<h2>Configuring icecast2 for YP support</h2>
+<h2>Configuring icecast2 for YP Support</h2>
 <p>First of all, icecast must have been built with YP support.  This is automatically done if you have libcurl installed.  If libcurl is not detected when icecats is compiled, then YP support is disabled.</p>
-<p>If icecast has been built with YP support, then the following configuration options control the YP directory settings :</p>
+<p>If icecast has been built with YP support, then the following configuration options control the YP directory settings:</p>
 <pre>
     &lt;directory&gt;
         &lt;yp-url-timeout&gt;15&lt;yp-url-timeout&gt;
@@ -25,7 +25,7 @@
 <br>
 <br>
 <br>
-<h2>Configuring Your Source Client for YP support</h2>
+<h2>Configuring Your Source Client for YP Support</h2>
 <p>This is usually covered in the source client documentation.  More specifically, the source client needs to provide the HTTP header ice-public:1 on connect in order to enable YP listing of the stream.</p>
 <p>If a mountpoint is being listed on a YP, then you will see some additional statistics relating to the YP such as last-touch, currently-playing, etc.</p>
 <br>

<p><p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'cvs-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.