ocket8888 opened a new issue, #7911: URL: https://github.com/apache/trafficcontrol/issues/7911
## This Feature Request affects these Traffic Control components: - Traffic Portal ## Description Perhaps in the DS creation modal where a type is selected, a description is shown based on the current selection. Proposed descriptions: Name | Content Routing | Description ----------------|----------------------|----------------------------------------------------------------------------------------------------- HTTP | HTTP Content Routing | <p>The Traffic Router DNS auth server returns its own IP address on DNS queries, and the client gets redirected to a specific cache in the nearest cache group using HTTP 302. Use this for long sessions like HLS/HDS/Smooth live streaming, where a longer setup time is not a problem.</p> DNS | DNS Content Routing | <p> The Traffic Router DNS auth server returns an edge cache IP address to the client right away. The client will find the cache quickly but the Traffic Router can not route to a cache that already has this content in the cache group. Use this for smaller objects like web page images / objects.</p> DNS_LIVE_NATNL | DNS Content routing | <p>Whereas for “standard” DNS content routing the objects are stored on disk, for this delivery service type the objects are stored on the RAM disks. Use this for linear TV. The MID tier is NOT bypassed for this type.</p> DNS_LIVE | DNS Content routing | <p>Same as DNS_LIVE_NATNL, but the MID tier is bypassed. HTTP_NO_CACHE | HTTP Content Routing | <p>Caches will not actually cache the content, they act as just proxies. The MID tier is bypassed.</p> HTTP_LIVE | HTTP Content routing | <p>Whereas for “standard” HTTP content routing the objects are stored on disk, for this delivery service type the objects are stored on the RAM disks. Use this for linear TV. The MID tier is bypassed for this type.</p> HTTP_LIVE_NATNL | HTTP Content routing | <p>Same as HTTP_LIVE, but the MID tier is NOT bypassed.</p> ANY_MAP | N/A | <p>ANY_MAP is not known to Traffic Router. For this deliveryservice, the “Raw remap text” field in the input form will be used as the remap line on the cache.</p> STEERING | HTTP Content Routing | <p>The Delivery Service will be used to route to other delivery services. The target delivery services Traffic Router and the routing weights for those delivery services will be defined by an admin or steering user. For more information see the steering feature documentation</p> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
