Re: "Too Busy" Error Needed

rdenny@netcom.com (Robert Denny)
Errors-To: listmaster@www0.cern.ch
Date: Thu, 9 Jun 1994 17:56:34 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <199406091553.IAA04758@netcom.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: rdenny@netcom.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: rdenny@netcom.com (Robert Denny)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: "Too Busy" Error Needed
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: text/plain; charset=US-ASCII
Content-Type: text/plain; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL23]
X-Mailer: ELM [version 2.4 PL23]

> From: vinay@eit.COM (Vinay Kumar)
>
> Another thing that you might want to add is that, return URL's for
> alternative mirror sites if the site you connected is busy.
> [...]

<begin inseparable text!>
Interesting idea. Along those lines, I thought about returning a "redirect"
which points right back to the object that was sought in the first place.
I junked it when I realized that it violates the most basic principals of
congestion control!
<end inseparable text :-) >

I see a potential problem with your suggestion which relates to relative
URLs. Unless the mirror site mirrors the entire original site, relative
URLs could break.

Another issue is synchronization. Suppose the primary site makes a change
to the document "web" resulting in link changes. Now let's say you're
reading around in the primary site's web, it gets busy, you get redirected
to the secondary site, and the link is invalid because the mirror site
hasn't been sync'ed since the changes at the primary.

    -- Bob