RE: ftp study (technical report)

"George D. Greenwade" <bed_gdg@shsu.edu> Wed, 30 September 1992 00:43 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa10889; 29 Sep 92 20:43 EDT
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id aa10885; 29 Sep 92 20:43 EDT
Received: from kona.CC.McGill.CA by NRI.Reston.VA.US id aa23652; 29 Sep 92 20:48 EDT
Received: by kona.cc.mcgill.ca (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA01055 on Tue, 29 Sep 92 19:06:40 -0400
Received: from niord.shsu.edu by kona.cc.mcgill.ca with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA01040 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Tue, 29 Sep 92 19:05:43 -0400
Received: by SHSU.edu (MX V3.1B) id 4987; Tue, 29 Sep 1992 08:00:04 CDT
Date: Tue, 29 Sep 1992 07:57:38 -0500
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: "George D. Greenwade" <bed_gdg@shsu.edu>
To: maffeis@ifi.unizh.ch
Cc: iafa@cc.mcgill.ca
Message-Id: <00961555.4B47D280.4987@SHSU.edu>
Subject: RE: ftp study (technical report)

On Tue, 29 Sep 92 11:17:28 MET, Silvano Maffeis <maffeis@ifi.unizh.ch>
posted:
> ifi-tr-92.13                   (available electronically as ifi-92.13.ps.Z)
>
> Abstract
>
> Global filesystems and new file transfer protocols are a great need and
> challenge in the presence of drastically growing networks. In this paper we
> present results obtained from an investigation of access to public files
> which took place over three months. This work visualizes first results on
> the popularity of public ftp  files, on common operations (deletions,
> updates and insertions) to public file-archives and on encountered
> filesizes. An index for measuring locality of reference to a resource is
> also proposed. The results show that most file transfers relate to only a
> small fraction of the files in an archive and that a considerable part of
> the operations to public files are updates of files. Further results are
> presented and interpreted in the paper.

I very sincerely hope that one of the "further results" deals with the
portability of the files on the polled systems, especially when the file is
(apparently) intended to be somewhat platform-independent (as I presume
this one to be).  I'm not suggesting 8+3; however, conceptualizing ftp to
always be to/from systems directly supporting multiple periods (as this
file suffers from; as does the draft.part.I and draft.part.II; as do any
number of files on anonymous ftp archives).  Once again, we return to the
"special characters" issue!

IMO, there is ABSOLUTELY NO REASON to believe that files on IAFA's have to
be actual working names on the host system (or any system!) without some
modification on the retrieving working system.  I have seen an increasing
number of friendly IAFA's using names such as ifi-92_13.ps_z (yes, even a
lowercase "z"), which are much nicer to have to deal with.  Narrow minded
Unix users will complain "but then I have to rename it ifi-92_13.ps.Z (or
whatever) to get it to uncompress".  Big deal -- users on single period
systems just want to GET the file (and will probably have to rename it as
well!).

This really needs to be thought about if IAFA's are really "a great need
and challenge in the presence of drastically growing networks."

Regards,   George
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
George D. Greenwade, Ph.D.                            Bitnet:  BED_GDG@SHSU
Department of Economics and Business Analysis         THEnet: SHSU::BED_GDG
College of Business Administration                    Voice: (409) 294-1266
P. O. Box 2118                                        FAX:   (409) 294-3612
Sam Houston State University              Internet:        bed_gdg@SHSU.edu
Huntsville, TX 77341                      bed_gdg%SHSU.decnet@relay.the.net
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%