Wikipedia

Real-Time Media Flow Protocol: Difference between revisions

Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Citation bot (talk | contribs)
Bots
5,872,833 edits
Alter: template type. Add: journal. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 677/2141
Citation bot (talk | contribs)
Bots
5,872,833 edits
Alter: title. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | #UCB_webform 1628/3834
 
(3 intermediate revisions by 3 users not shown)
Line 2:
 
==Operation==
RTMFP allows users of live, real‐time communications, such as [[social networking service]]s and multi‐user games, to communicate directly with each other using their computer's microphone and webcam. RTMFP is a [[peer-to-peer]] system, but is only designed for direct end user to end user communication for real-time communication, not for file sharing between multiple peers using segmented downloading..<ref>[https://www.adobe.com/products/flash-media-enterprise/rtmfp-faq.html RTMFP FAQ]</ref> Facebook uses this protocol in its Pipe application<ref>{{Cite web |url=http://www.pipe.com/how/ |title=Pipe |access-date=2013-11-23 |archive-date=2013-12-03 |archive-url=https://web.archive.org/web/20131203000113/http://www.pipe.com/how/ |url-status=dead }}</ref>
 
RTMFP enables direct, live, real‐time communication for applications such as audio and [[Videoconferencing|video chat]] and multi‐player games. RTMFP flows data between the end‐user
Line 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.
 
Line 32:
==References==
{{reflist|1}}
 
 
 
{{Adobe Flash}}
Retrieved from "https://en.wikipedia.org/wiki/Real-Time_Media_Flow_Protocol"