Content deleted Content added
→History: Adding missing merge template |
Citation bot (talk | contribs) Alter: title. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | #UCB_webform 1628/3834 |
||
(15 intermediate revisions by 13 users not shown) | |||
Line 1:
The '''Secure Real-Time Media Flow Protocol''' ('''RTMFP''') is a [[protocol suite]] developed by [[Adobe Systems]] for encrypted, efficient [[multimedia]] delivery through both [[client–server model|client-server]] and [[peer-to-peer]] models over the [[Internet]]. The protocol was originally [[proprietary protocol|proprietary]], but was later opened up and is now published as
==Operation==
RTMFP
clients and not the server, bandwidth is not being used at the server. RTMFP uses the [[User Datagram Protocol]], (UDP) to send video and audio data over the Internet, so needs to handle missing, dropped, or out of order packets. RTMFP has two features that may help to mitigate the effects of connection errors.
▲RTMFP will reduce the bandwidth costs for direct, live, real‐time communication solutions, such as audio and [[Videoconferencing|video chat]] and multi‐player games. Because RTMFP flows data between the end‐user
'''Rapid Connection Restore:''' Connections are re‐established quickly after brief outages. For example, when a [[wireless network]] connection experiences a dropout. After reconnection, the connection has full capabilities instantly.
'''IP Mobility:''' Active network peer sessions are maintained even if a client changes to a new [[IP address]]. For example, when a laptop on a wireless network is plugged into a wired connection and receives a new address.
==Difference between RTMP and RTMFP==
Line 24 ⟶ 16:
[[User Datagram Protocol]] (UDP),<ref name="id" /> whereas [[Real-Time Messaging Protocol]] (RTMP) is based on [[Transmission Control Protocol]] (TCP).
UDP‐based protocols have some specific advantages over TCP‐based protocols when delivering live [[streaming media]], such as decreased latency and overhead, and greater tolerance for dropped or missing packets, at the cost of decreased reliability.
Unlike RTMP, RTMFP also supports sending data directly from one [[Adobe Flash Player]] to another,
without going through a server. A server‐side connection will always be required to establish the initial connection between the end‐users and can be used to provide server‐side data execution or gateways into other systems. The user of a [[Adobe Flash Media Server|Flash Media Server]] will also be required to authorize network address lookup and [[NAT traversal]] services for the clients to prevent Flash Player from being used in an unmanaged way.
== Application-level multicast ==
Flash Player 10.0 allowed only one-to-one communication for P2P, but from 10.1 application-level [[multicast]] is allowed. Flash Player finds appropriate distribution route ([[overlay network]]), and can distribute to the group, which is connected by P2P.
== History ==
RTMFP's underlying protocols are the result of Adobe's acquisition of [[Amicima]] in 2006; strong architectural similarities exist between RTMFP and Amicima's [[GNU General Public License|GPL]]-licensed '''Secure Media Flow Protocol (MFP)'''.
Line 41 ⟶ 32:
==References==
{{reflist|1}}
{{Adobe Flash}}
|