Scribd Logo
Upload

Welcome to Scribd!

  • Untitled

    Uploaded by

    gyanendra_webmaster
    5 views1 page
    Traditional CDNs were designed to accelerate static objects on a website by architecting the site to store the static objects in a different host location. This separati on was crucial, as the CDN handled only the static pages, and the non-cacheable objects were served directly from the origin server. However, this approach is inherently inefficient, as it requires modification of the existing site.

    Original Description:

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    Traditional CDNs were designed to accelerate static objects on a website by architecting the site to store the static objects in a different host location. This separati on was crucial, as the CDN handled only the static pages, and the non-cacheable objects were served directly from the origin server. However, this approach is inherently inefficient, as it requires modification of the existing site.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    5 views1 page

    Untitled

    Uploaded by

    gyanendra_webmaster
    Traditional CDNs were designed to accelerate static objects on a website by architecting the site to store the static objects in a different host location. This separati on was crucial, as the CDN handled only the static pages, and the non-cacheable objects were served directly from the origin server. However, this approach is inherently inefficient, as it requires modification of the existing site.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Traditional CDNs were designed to accelerate static objects on a website by arch itecting the site to store the static

    objects in a different host location, away from the main site, CNAME-ing only that host to the CDN provider. This separati on was crucial, as the CDN handled only the static pages, and the non-cacheable objects were served directly from the origin server. However, this approach is i nherently inefficient, as it requires modification of the existing site. It is a lso error prone as links internal or external may still direct to the original host.

    You might also like