I think this is a good idea -- the really important capability it
enables is this: if I (I == ``real user using WWW mechanisms for real
work'') set up an HTTP server that people at my site will need to get
to at all times, then with this mechanism I could *at the very least*
tell my WWW clients about alternate servers that I also set up.
A big advantage is that nothing major (i.e., HTTP or HTML) would have
to be changed.
As for the problems: (1) it is true that to be useful in the general
sense a master list would have to be maintained, but each local site
would only have to pull down a new one every few months -- these
things aren't going to change that often (expansion is more likely),
and (2) is a problem with any change of anything at this point, which
is why I think a very lightweight change (like this) would be best.
Marc
-- Marc Andreessen Software Development Group National Center for Supercomputing Applications [email protected]