Built-in bitmaps as URNs

• Mail folder: WWW Talk Jul-Oct 1993
• Next message: Dave_Raggett: "Re: who determines formatting"
• Previous message: Willem van Leeuwen: "Re: virtual documents"

From: Dave_Raggett <dsr@hplb.hpl.hp.com>
Message-id: <9307081121.AA18831@manuel.hpl.hp.com>
Subject: Built-in bitmaps as URNs
To: www-talk@nxoc01.cern.ch
Date: Thu, 8 Jul 93 12:21:07 BST
Mailer: Elm [revision: 66.36.1.1]
Status: RO

I liked Marc's suggestions for <LI IMG=...> and will add it to the
proposed Internet Draft for HTML+ so that you guys can pick over it
at the workshop, unfortunately, I can't come :-(.

The discussion about "built-in" bitmaps seems to have forgotten URNs.
By designating the common bullets/icons as URNs it all becomes a mere
matter of caching strategy.

The URN mechanism provides a protocol for resolving a URN to the nearest
available URL, similar I guess to the domain name service for host names.
By making the local URN name server cooperate with a local HTTP server,
frequently requested URNs will be served directly from the local cache.
The cache management strategy doesn't have to be completely automatic,
and you could designate some objects to be cached using a config file.

For red-hot performance, the first point of access for the URN name service
would be a permanently loaded process on your own machine (avoiding inetd
fork/exec delay), with objects in the local cache being accessed directly
as files.

Dave