readme

symbian下ffmpeg编程。。废了好大劲下下来的！。

Using the video server
======================

The video server needs a running ordinary web server, in order to publish
archived streams and preview images.

It needs one TCP port for receiving the streams from clients and one port
for providing info feeds about the current live and archived streams and
for serving the live streams to users.

If no authentication options are given, no authentication is required
from the clients.

Running "./movino-daemon -h" gives a short summary of the available command
line options. They are:

	-i port		Sets the port for receiving stream data from
			clients. (Default 30710)

	-o port		Sets the port for serving all content, both
			info xml feeds and video streams. (Default 24536)

	-n hostname	Sets the which hostname should be used for
			accessing the server. It is used for creating
			the URLs to the live video streams.

	-d dir		Sets the directory where the server stores
			the archived video files, previews and
			archive stream metadata.

	-u url		Sets the URL prefix to the archive directory.
			The server assumes that web clients can
			access the files within the archive directory
			by appending the file name within the archive
			directory to this URL.

	-p file		Loads a list of usernames and passwords from
			the given file. An example of this kind
			of file is given in passwords-example.

	-a url		Sets the server to use a drupal site with
			the movino drupal module for authentication.
			The URL given is the precise URL to the
			authentication service.

	-f format	Chooses which format the server encodes to.
			Currently, the only supported alternatives
			are ogg, flv and mpeg. (Default ogg)

	-l file		Writes to a log file instead of to stdout.

	-m g,ps,s	Limit the number of concurrent streams.
			g denotes the maximum global number of client
			video streams, ps denotes the maximum number
			of clients per video stream, s denotes the
			maximum number of sources. Setting a
			value to 0 menas no limit. (Default 0,0,0)

	-b address	Bind the content serving http server to this
			adress. (Default all addresses)

	-s secretfile	Load a shared secret from the given file.
			This is used for authentication of commands
			over the http interface. The authentication
			is based on HMAC-MD5, and therefore the
			secret file should optimally be 64 bytes
			large.


HTTP interface
==============

The server provides information on the current live streams on the
URL http://<server>:<port>/live.xml by default, and information on
the archived streams on /archived.xml. The URLs of the actual video
streams are mentioned in these XML feeds.

By uncommenting the line mentioning MESSAGE_NAME in main.cpp, the
server also accepts messages to the clients on the URL /message (or
whatever MESSAGE_NAME is set to). The message is sent by normal form
encoded data, either as GET or POST. The field id must be present,
specifying which client stream to send the message to. (This matches
the id element in the live stream XML feed.) The field msg contains
the actual message. An example of a message query string:

http://server:24536/message?id=1234567890abcdef&msg=Hello+World%21

To restrict the access to this messaging service (e.g. to restrict
its usage to a web interface), a secret key file can be specified.
The key file is used as a key to a HMAC-MD5, and therefore optimally
should be 64 bytes long. The same secret key file should be available
to the video server and to the party creating the queries, and the
secret key file can be any random data. If this file is specified, the
query also needs to contain a timestamp field. This simply contains
the unix timestamp value for the time when the query was sent/generated.
If this differs more than 10 seconds from the timestamp when this is
verified, the query is discarded.

When the query has been constructed, the HMAC-MD5 of the query string
is calculated using the secret key. This hash is appended to the query
string.

An reference example query for a secret key file consisting of 64
zero bytes would be:

http://server:24536/message?id=1234567890abcdef&msg=Hello+World%21&timestamp=1208027684&hash=baf21dd8c9b0ecbc9bad1dc863a74fc5

That is, the HMAC-MD5 of 

id=1234567890abcdef&msg=Hello+World%21&timestamp=1208027684

is baf21dd8c9b0ecbc9bad1dc863a74fc5, using the given secret key
of 64 zero bytes.