[9790] in www-talk@info.cern.ch
Re: HTTP-NG Server & Client Mechanisms
daemon@ATHENA.MIT.EDU (Darren New)
Wed Feb 21 15:22:37 1996
Date: Wed, 21 Feb 1996 09:49:24 -0800 (PST)
From: Darren New <dnew@yuan.fv.com>
Reply-To: dnew@fv.com
To: BearHeart / Bill Weinman <bearheart@bearnet.com>
Cc: www-talk@w3.org
In-Reply-To: <2.2.32.19960221173519.007077e4@204.145.225.20>
Resent-From: www-talk@w3.org
On Wed, 21 Feb 1996, BearHeart / Bill Weinman wrote:
> I'm confused. What does this have to do with client performance?
> What can a client do about some unknown piece of hardware between it
> and its server?
Well, for example, Netscape's browser (and others) opens multiple
connections at once, progressively displays interlaced files, and so on.
A client that keeps connections open between fetches will be faster than
one that closes connections for each fetch. A client capable of using
proxies might be faster than a client not capable of using proxies.
Of course, nothing you can do with a client is going to fix Sprintlink. :-)
--
Darren New / Dir. of Custom Software Design / First Virtual Holdings Inc.
Anyone can buy and sell information over the internet for real money TODAY!
http://www.fv.com or info@fv.com -=|=- PGP key: finger dnew@yuan.fv.com
This message brought to you by the letter T, and the number 1.
