Re: Slow HTTP Responses

• Mail folder: WWW Talk Jan 94-present
• Next message: R. Michael Van Dyk: "Whitespace | Fonts | HTML vs. page layout"
• Previous message: George Phillips: "Slow HTTP Responses"
• Reply: George Phillips: "Re: Slow HTTP Responses "
• Reply: Lou Montulli: "Re: Slow HTTP Responses"
• Reply: Rich Wiggins: "Re: Slow HTTP Responses"

Message-id: <199401131846.MAA02762@austin.BSDI.COM>
To: www-talk@www0.cern.ch
Subject: Re: Slow HTTP Responses 
In-Reply-To: George Phillips's message of 13 Jan 1994 01:55:00 PST.
Organization: Berkeley Software Design, Inc.
Date: Thu, 13 Jan 1994 12:46:16 -0600
From: Tony Sanders <sanders@BSDI.COM>
Content-Length: 587

> 	Status: 20 % of search done
> 	 ... and a bit later
> 	Status: 100 % done!

WOW!!!!!! Does this mean that you have solved the halting problem?????
Would you please explain how you are supposed to know what 20% done means?  :-)

Anyway, the point is that you could do this for timeout related functions
but in that case you would be much better off just returning the timeout
value to the client.

The *only* useful thing you could do is print warm fuzzies, but then the
browser could really just fake that and everyone would be happy 99% of the
time with 1% of the effort.

--sanders