Real Data Transport

Real Data Transport (RDT) is a <a href="/facts/Proprietary_protocol/o902Cmmh">proprietary</a> <a href="/facts/Transport_protocol/UmIGUCeK">transport protocol</a> for the actual audio-video data, developed by <a href="/facts/RealNetworks/XenxRXL2">RealNetworks</a> in the 1990s. It is commonly used in companion with a control protocol for <a href="/facts/Streaming_media/4rPhSq0Y">streaming media</a> like the <a href="/facts/IETF/tIcCsFhX">IETF</a>'s <a href="/facts/Real_Time_Streaming_Protocol/he6ChB16">Real Time Streaming Protocol</a> (RTSP).
A non-proprietary alternative for RDT is IETF's <a href="/facts/Real-time_Transport_Protocol/YKQK1RK2">Real-time Transport Protocol</a> (RTP), which is also implemented in RealNetworks players.
As reported in a 2002 book about firewalls, RDT used two unidirectional <a href="/facts/User_Datagram_Protocol/dxLU0D6q">UDP</a> connections, one for the data sent from the server to the client and another in the opposite direction for retransmission requests. The same book reported that RealNetworks' G2 server used RDT in this configuration by default. Another 2003 book reported that RDT was also seen carried over <a href="/facts/Transmission_Control_Protocol/WW4sPrt9">Transmission Control Protocol</a> (TCP), as a fall-back mechanism.
RDT is now included as part of the <a href="/facts/Helix_Community/jrofyQmr">Helix Community</a> project.

Real Data Transport open-in-new

Real Data Transport