Changes between Version 17 and Version 18 of Documentation/VLC

Timestamp:

Apr 30, 2010, 6:08:33 PM (14 years ago)

Author:

stud-hock

Comment:

--

Documentation/VLC

@@ -74 +74 @@
 In this section we describe the parameters of the mcpo-vlc plugin and some usage scenarios which demonstrate the strength of the mcpo approach.
 
-Vlc-mcpo uses a spontaneous virtual network (SpoVNet) for distributing the video content. Each SpoVNet have to consist of 0-1 senders and 0-N receivers. The connection procedure does not depend on the role (sender/receiver) one instance has. This can confuse a little in the beginning, as on most streaming protocols the role defines whether one instance is client or server.
+Mcpo-vlc uses a spontaneous virtual network (SpoVNet) for distributing the video content. Each SpoVNet have to consist of 0-1 senders and 0-N receivers. The connection procedure does not depend on the role (sender/receiver) one instance has. This can confuse a little in the beginning, as on most streaming protocols the role defines whether one instance is client or server.
 
 
 ==== Parameters ====
-The vlc-mcpo plugin takes three connection parameters. source-port:destination-address:destination-port (e.g. 1234:localhost:5000)
+The mcpo-vlc plugin takes three connection parameters. source-port:destination-address:destination-port (e.g. 1234:localhost:5000)
 
 The "source-port" provides an entry point for other instances to the SpoVNet our instance is (or will be) in.
@@ -87 +87 @@
 
 ==== Creating a SpoVNet ====
-At first we need an initial SpoVNet, consisting of a single vlc-mcpo instance. This instance can be either server or client but must be accessible from (at least) the second instance. On the first instance we have to set the source-port. (Destination-address and -port can be set but as long as there is no other instance listening there, setting this parameters has no effect.)
+At first we need an initial SpoVNet, consisting of a single mcpo-vlc instance. This instance can be either server or client but must be accessible from (at least) the second instance. On the first instance we have to set the source-port. (Destination-address and -port can be set but as long as there is no other instance listening there, setting this parameters has no effect.)
 
 On the second instance, destination-address and -port must be set adequate. It can also set the source-port to act as an entry point later.