Commit 88636e55 authored by Marc Ariberti's avatar Marc Ariberti

* more examples in vlcs.conf

* added the 'tar' target in Makefile in order to make the build of the
archive for the release more easy

* updated README file for the release : version 0.2.0
parent 99f8bd53
......@@ -7,5 +7,8 @@ all: vlcs
vlcs: vlcs.c vlcs.h
$(CC) -O3 -g -I. -Wall -o $@ vlcs.c
tar:
tar cvzf vlcs.tar.gz vlcs.c vlcs.h vlcs.conf Makefile README COPYING
clean:
-rm -f vlcs
......@@ -2,33 +2,46 @@
*
* Authors : Marc ARIBERTI <marcari@videolan.org> (current maintainer)
* Christophe MASSIOT <massiot@via.ecp.fr>
*
* Version : 0.2.0
*
WARNING: difference with version 0.1.0
The former vlcs supported the older and the newer vlc syntax for network
streaming (ts:// and udp://). Now you should only use the newer one and upgrade
the vlc. This has been made to make the config file more simple. Now you
just have to put what you would type on the command line for the vlc, and
not vls' IP, port... anymore, which were not relevant all of the time.
--
When we began developing the multicast technology for VideoLAN, we wanted
an easy way to tell the client what is the multicast address associated to
a channel. When the vlc wants to get a new channel, it sends a request
to the VLCS and the VLCS gives an answer like : udp://@239.255.255.42
When we began developing the multicast technology for VideoLAN, we wanted an
easy way to tell the client what is the multicast address associated to a
channel. When the vlc wants to get a new channel, it sends a request to the VLCS
and the VLCS gives an answer like : udp://@239.255.255.42
I decided to do this way for sending the multicast address to the client
because it did not required any modification inside the vlc.
I decided to do this way for sending the multicast address to the client because
it did not required any modification inside the vlc.
The protocol is the same whether the VLCS is a complete VLANserver or
this miniVLCS.
The protocol is the same whether the VLCS is a complete VLANserver or this
miniVLCS.
The VLANserver would change the client's VLAN by sending a SNMP request
to the switchs are answers when everything is ok. This mini-VLCS answers
immediatly with the multicast address. Then the client knows it is a
multicast address and sends request to the network itself to received
the multicast stream.
The VLANserver would change the client's VLAN by sending a SNMP request to the
switchs are answers when everything is ok. This mini-VLCS answers immediatly
with the multicast address. Then the client knows it is a multicast address and
sends request to the network itself to received the multicast stream.
This miniVLANSERVER can also be used with broadcasted streams, it
will help the client to decide with stream to catch.
This miniVLANSERVER can also be used with broadcasted streams, it will help the
client to decide with stream to catch.
This miniVLCS is based on the VLCS part of the miniVLANSERVER. That
part has been originally written by C. Massiot.
This miniVLCS is based on the VLCS part of the miniVLANSERVER. That part has
been originally written by C. Massiot.
How to install it :
~~~~~~~~~~~~~~~~~~~
* Decompress the archive
* change into the directory
......
......@@ -2,7 +2,7 @@
* vlcs.c: VideoLAN Channel Server socket facility
*****************************************************************************
* Copyright (C) 2001 VideoLAN
* $Id: vlcs.c,v 1.3 2002/03/20 15:06:27 marcari Exp $
* $Id: vlcs.c,v 1.4 2002/03/24 23:30:09 marcari Exp $
*
* Authors: Christophe Massiot <massiot@via.ecp.fr>
* Marc Ariberti <marcari@via.ecp.fr>
......@@ -192,6 +192,8 @@ void socket_Send( struct sockaddr_in * p_sa, char * psz_message )
{
time_t tm;
time(&tm);
/* TODO: remove this ugly kludge */
fprintf(stderr, "%s : %s => %s\n",
asctime( localtime( &tm ) ),
inet_ntoa( p_sa->sin_addr ),
......
I: nostream
udp://vls2@0:1234
udp://vls2@0:2345
udp:@239.255.255.42
udp:@239.255.255.43
udp:@239.255.255.44
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment