<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta name="Author" content="Bart.Kerver@SURFnet.nl" />
<meta name="Keywords" content="Webbased configuration of a distributed set of VideoLAN Servers" />
<title>DVLSM - Distributed VideoLANServer Management</title>
<link rel="stylesheet" type="text/css" href="main.css" />
</head><br><br><h1>Welcome to Distributed VideoLAN Server Manager</h1><br>
<body>
<p>
<h3>What is DVLMS</h3>
DVLMS stands for <i>D</i>istributed <i>V</i>ideo<i>L</i>AN <i>S</i>erver <i>M</i>anagement. DVLMS is a webbased interface to control
several <a href="http://www.videolan.org/vls/">VideoLAN-servers</a> distributed through a network with the ease of a click of a mouse. DVLSM makes it very easy for end-users to
get access to videodata available on some VLS server without having to learn the VLS command interface. DVLSM is not just build to
manage VLS-servers, but to create a Video-on-Demand solution for <a href="http://www.videolan.org/vlc/">VideoLAN MediaPlayer (VLC)</a> and <a href="http://www.aminocom.com/">Amino SetTopBoxes</a> (and so on...). Just install the
source code, compile, start the VLS server and let the DVLSM add a servers content to the system by the click of a link.
</p>
<p>
<h3>Requirements to run DVLSM</h3>
DVLMS consists out of two parts: a interface module to operate within VLS server and a webbased portal. The interface module
is basically an interface for the webservice to talk to a regular VLS server. The webbased portal is a set of PHP scripts to
communicate with the database backend and the DVLSM interface module. All DVLSM requires to manage a system, is internet access to the machine and an account to control VLS.<br>
</p>
<p>
<h3>DVLSM features</h3>
DVLSM is currently supporting these features:<br>
<ul>
<li>open source using standards like PHP, Apache, mySQL and VLS CVS;</li>
<li>native VLS C++ code, available as an interface module;</li>
<li>fully database driven (mySQL);</li>
<li>unlimited amount of VLS servers with server specific credentials such as username, password and port</li>
<li>overview of active VLS servers;</li>
<li>overview of assets (with its provider) for a specific VLS server;</li>
<li>overview of all programs running on a specific VLS server;</li>
<li>auto learn content available on a server by spidering the programs</li>
<li>start a program on unicast, multicast both IPv4 and IPv6;</li>
<li>all native VLS command available through a simple query.</li>
</ul>
DVLSM is will support these features in a future release:<br>
<ul>
<li>(network-) load balancing of assets over multiple servers;</li>
<li>enhanced control over VLS core, such as killing dead channels;</li>
<li>ability to add programs;</li>
<li>ability to choose HTTP-progressive download as an alternative stream;</li>
<li>make it available as a webservice (XML-RPC);</li>
<li>user based profiles and content protection;</li>
<li>additional information on assets;</li>
<li>search for assets over all servers.</li>
</ul>
<p>
<h3>Configuration and installation of DVLSM</h3>
Soon to come...<br><br>
To get the DVLSM source running in VLS, make some adaptations to the Makefile.opts and /core/buffers.cpp and /core/buffers.h. <br>
To get the webbased portal running, install <a href="http://www.apache.org/">Apache</a> with <a href="http://www.php.net/">PHP</a> and <a href="http://www.mysql.com/">mySQL</a> support.
</p>
</body>
</html>