Streaming protocols


In one such mechanism the web server does not terminate the response to the client after data has been served. This differs from the typical HTTP cycle in which the response is closed immediately following data transmission. The web server leaves the response open such that if an event is received, it can immediately be sent to the client. Otherwise the data would have to be queued until the client's next request is made to the web server. The act of repeatedly queing and re-requesting information is known as a Polling mechanism. HTTP protocol usually uses port 80 or 8080.

MMS - Microsoft Media Services

Microsoft's streaming server uses the Microsoft Media Services (MMS) protocol (also called NetShow Services) to transfer unicast data. MMS can be transported via UDP or TCP (MMSU and MMST protocols). If the Windows Media Player client cannot negotiate a good connection using MMS over UDP, it will resort to MMS over TCP. If that fails, the connection can be made using a modified version of HTTP (always over TCP). This is not as ideal for streaming as MMS over UDP, but ensures connectivity nonetheless. The default protocol for streaming Windows Media is not MMS, but RTSP. The default port for MMS is 1755.

RTSP - Real Time Streaming Protocol

The Real Time Streaming Protocol (RTSP), developed by the IETF and published in 1998 as RFC 2326, is a protocol for use in streaming media systems which allows a client to remotely control a streaming media server, issuing VCR-like commands such as "play" and "pause", and allowing time-based access to files on a server. Some RTSP servers use RTP as the transport protocol for the actual audio/video data. Many RTSP servers use RealNetworks's proprietary RDT as the transport protocol. RTSP can be transported via UDP or TCP (RTSPU and RTSPT protocols). The default port for RTSP is 554.

You must have Vlc plugin instaled. Don't try streams that begins with rtmp://$OPT:rtmp-raw=. They are reserved for flash players.