This works well in cases where nobody outside the site is likely to link
to the content. Ie, you can't control/update external references
(bookmarks and links). http://www.acme.com/xxx0001.zzz existing today
and not tomorrow is bad (it causes broken links). But with the right
web server, xxx0001.zzz could automatically become a redirect to the
new content (ie, consult database and find that the latest version of
xxx is 0002).
> NEW VISION: Web servers should automatically create unique names for their embedded
> content. These names can, for example, contain a content signature in the URL name,
> with an infinite expire time. Users never see these names; they appear
> for example, in embedded <img> </img> HTML references. Akamai uses this concept in their
> free flow service. This usage obviates the need for web caches and browser caches to
> validate cached content. This eliminates the staleness in browser caches and web caches.
>
> How does this work? These days, most HTML container pages are personalized and
> non-cachable anyway ( e.g. http://my.yahoo.com). What the web servers should do is to
> take gifs such as http://www.yahoo.com/yahoo.gif and internally map it to a unique name
> that depends on the gif's content signature: http://www.yahoo.com/yahoo.gif/005662256999cc801dde6e86ac12031f
> This uniquely named URL no longer needs to be verified. If the URL changes content, the
> URL in the container page changes: http://www.yahoo.com/yahoo.gif/4cfa72a3d395d8217142e06ae6042188
>
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:08 MDT
