2.1.5.5 WMSP: Logical Dependencies and Relationship to Other Protocols
The Windows Media HTTP Streaming Protocol (WMSP) depends on HTTP 1.0, as specified in [RFC1945]. The pipelined mode of the protocol can be used only if the client, the server, and any intermediate HTTP proxy servers support the pipelining feature of HTTP 1.1, as specified in [RFC2616].
This protocol can be used instead of the Microsoft Media Server (MMS) Protocol (MMSP), as specified in [MS-MMSP]. This protocol can also be used instead of the Real Time Streaming Protocol (RTSP) Windows Media Extensions (RTSP-WME) specified in [MS-RTSP]. However, it is important to note that although these two other protocols allow the multimedia data to be transmitted over either UDP or TCP, Windows Media HTTP Streaming Protocol (WMSP) allows multimedia data to be transmitted only over TCP because HTTP always uses TCP. WMSP is a good choice, where the multimedia data is passed through a proxy or a firewall, because it uses HTTP, which is typically configured to pass through the proxy or firewall.
WMSP is mutually exclusive from Windows Media HTTP Push Distribution Protocol (WMHTTP), MMSP, Windows Media Services (MSB, MSBD), and RTSP-WME. When WMSP is used, it is not possible to use the preceding protocols. It is possible, however, to use Windows Media Log Data Structure (WMLOG) concurrently with WMSP.