Message-Id: <email@example.com> Date: Fri, 16 Jan 1998 13:46:39 -0800 From: Alex Fabrikant <firstname.lastname@example.org> To: email@example.com Subject: Re: Suggestion: ALTHREF attribute <SNIP> If you think about this closely, it does sound as if a new META element is being thought of: <META NAME="MIRROR" HREF="http://www.mymirror.com"> If this was in a page originating in the .co.uk domain, which was slow, and being viewed in american .com domain, the browser could quite easily give an option to change. Further mirrors could be included: <META NAME="MIRROR" HREF="http://www.mymirror.com" HREF2="http://www.mymirror.com.au" HREF3="http://www.mymirror.com.tw"> You get the general idea. The only problem it does not solve is if the source document itself cannot be retrieved for some reason or another. That could be up to a supplementary HTTP server redirecting requests to an appropriate mirror, but that's for the hardware guys to work on, not me. </SNIP> I don't quite see why this should be handled by the HTTP server. An ALTHREF (or whatever you want to call it) should accept a comma(?)-delimetered list of URIs, with a single function - providing the client with an alternative address to load in CASE OF AN ERROR. A META or a LINK-based system can be implemented as well, allowing for definition of mirror sites, but this would not relate to the same problem -- Alex Fabrikant firstname.lastname@example.org !