Hi JvD,

The difference between the two is: the former doesn’t serve the content under 
the paths other than “/vod/” and “/live/”.

For example, for the request 
“http://traffic-server.sports.ipcdn.com/path/file”, the former doesn’t serve it 
while the latter does serve it.

Regarding the use case, this is useful if:

Under the same domain name, the contents under some paths are set by one 
configuration and the contents under some other paths are set by another 

For example,

Different “Regex remap expression” can be configured for 
“http://traffic-server.sports.ipcdn.com/vod/” and 

Different traffic caches can be assigned for 
“http://traffic-server.sports.ipcdn.com/vod/” and 

Some different configuration items become possible because separated delivery 


On 30/11/2016, 23:23, "Jan van Doorn" <j...@knutsel.com> wrote:

    Hi Jifeng,
    I'm still confused, bear with me please. 
    The Google doc example has
    map http://traffic-server.sports.ipcdn.com/vod/     
    map http://traffic-server.sports.ipcdn.com/live/     
    But, isn't that the same as 
    map http://traffic-server.sports.ipcdn.com/     http://origin.server.com/
    If you want to send the /live to RAM and the /vod to disk, they can't be in 
the same deliveryservice table entry, since all those type if things are set 
    Can you elaborate on the use case you are trying to solve?
    > On Nov 30, 2016, at 04:16, Jifeng Yang (jifyang) <jify...@cisco.com> 
    > Hi,
    > Different delivery services can be configured with different domain names 
now. In some cases, different delivery services with same domain name and 
different path prefixes are needed. These delivery services can have different 
    > The problem and a solution are described in the document 
    > The issue and PR for this:
    > Issue: https://issues.apache.org/jira/browse/TC-55?jql=project%20%3D%20TC
    > PR: https://github.com/apache/incubator-trafficcontrol/pull/108
    > Thanks,
    > Jifeng

Reply via email to