Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a22c43847d115751

Jump to content

Real Data Transport

From Wikipedia, the free encyclopedia

Real Data Transport (RDT) is a proprietary transport protocol for the actual audio-video data, developed by RealNetworks in the 1990s. It is commonly used in companion with a control protocol for streaming media like the IETF's Real Time Streaming Protocol (RTSP).[1]

A non-proprietary alternative for RDT is IETF's Real-time Transport Protocol (RTP), which is also implemented in RealNetworks players.[1]

As reported in a 2002 book about firewalls, RDT used two unidirectional UDP 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.[2] Another 2003 book reported that RDT was also seen carried over Transmission Control Protocol (TCP), as a fall-back mechanism.[1]

RDT is now included as part of the Helix Community project.

References

[edit]
  1. 1 2 3 Mauricio Arregoces; Maurizio Portolani (2003). Data Center Fundamentals. Cisco Press. p. 460. ISBN 978-1-58705-023-7.
  2. Syngress (11 December 2002). Cisco Security Specialists Guide to PIX Firewall. Syngress. p. 155. ISBN 978-0-08-047655-1.
[edit]