Re: Quality problems - AGREE!
"James (Eric) Tilton" <jtilton@willamette.edu>
Errors-To: listmaster@www0.cern.ch
Date: Thu, 14 Apr 1994 23:02:48 --100
Message-id: <Pine.3.89.9404141325.A6936-0100000@jupiter>
Errors-To: listmaster@www0.cern.ch
Reply-To: jtilton@willamette.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: "James (Eric) Tilton" <jtilton@willamette.edu>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Quality problems - AGREE!
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
Content-Length: 927
I can give one reason for giving the relocation message -- you may be
trying to migrate a server from one location to another. In that
instance, you'll want to leave up notices of the change for a while (long
enough for people to fix their pointers), but you don't want to leave up
the old server permanently. After all, what's the point of moving the
server if you've still got the old server giving out redirections? :)
-et
On Thu, 14 Apr 1994 prosyst@Onramp.NET wrote:
> Jacob,
>
> I totally agree; plus, instead of giving a message like you
> sometimes get from a phone company, for example:
>
> "Sorry you must NOT dial a "1" in front of this number..."
> Why not just assume "no 1" and not bother with the message.
>
> In the case of "this xxx relocated to yyy," why not just
> link to "yyy" instead of bothering with the message, or,
> notify with the message and still link them there.
>