If this is a good idea, to extend the syntax associated with HREF, that is.
Then the most generic approach would be to let the HREF-attribute be the
first choice and then let HREF2, HREF3 and so on be the subsequent choices if
the first failed. Wouldn't it?
A possible approach to select further alternatives if the value of HREF is
unreachable is to let any attribute of the form /HREF[0-9]+/ be used later.
Preferably in numerical sorted order.
An important question is when these alternatives should be used. After a
timeout? After a timeout and certain status-codes? If the accessed data is
unusable in some sense?
Furthermore, is it at all allowed in SGML to have "generic" attributes like
this?
Nothing but questions but maybe some of them is good for the discussion.
/G
--
G|ran \berg Ludd, University of Lulea, SWEDEN Student MSc CS
K}rhusv{gen 5:601 http://www.luth.se/~goggi/ Adm./CoAdm. of
S-976 54 Lulea goggi@dc.luth.se {www,wais,ftp,gopher}.luth.se
______________________________________________________________________________