> Also, Netscape (and other browsers) open and close the ftp
> connection for each transfer, whereas the standard ftp clients
> maintain the control connection for the entire session. This
> means that your browser must *fight* the traffic for each directory
> listing, file transfer, etc.
I don't know about the code in netscape, but the stock libwww from CERN
has _always_ cached the control connection. Emacs-w3 uses ange-ftp or
efs to do the ftp work, and they also cache the connection.