RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
draw.io Diagram diagramName uml.drawio diagramWidth 787 revision 2
draw.io Diagram diagramName
Refer Client Fail-Over Behavior to know how clients should behave using the linear redundancy features of the CDN.
Gliffy Diagram macroId 5ae6a1e3-9ceb-4a0b-844f-dd7a0fb67588 displayName AAMP_DASH_license_retrylogic_uml_Gliffy name uml pagePin 7
Gliffy Diagram macroId fcc0e893-2552-432b-87e3-843a49b6be42 name AAMP DASH Manifest Download Retry logic.drawio diagramWidthpagePin 8011 revision 2
draw.io Diagram diagramName Gliffy Diagram macroId 31d14170-36e9-4a10-b462-704449b96b46 name AAMP Fragment Download Retry logic (without TSB)-Gliffy.drawio diagramWidthpagePin 7381 revision 2
gliffy draw.io Diagram diagramName Gliffy Diagram macroId b1f687d6-9b45-4c41-a826-0df4e114f592 name AAMP HLS Main Manifest Download Retry logic (without TSB)-Gliffy.drawio pagePindiagramWidth 1755
macroIdrevision 2
draw.io Diagram | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
http 4xx (and 502 Bad Gateway) are considered fatal errors for a given download attempt. No retry of the same URL will be performed. For other 5xx failures, single retry will be attempted after configurable delay (default 1s).
...
Show If | ||
---|---|---|
| ||
FOG is a separate service involved with Client-Side IP Linear Time Shift Buffer (TSB) support, caching fragments and generating virtual playlists that grow and eventually cull. As such, it shares many of the same responsibilities and behaviors as AAMP running in AAMP-only playback scenarios. FOG configuration includes:
|