Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!lll-winken!gauss.llnl.gov!casey
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: FTP "STRU VMS" extension
Message-ID: <20330@lll-winken.LLNL.GOV>
Date: 13 Feb 89 22:15:03 GMT
References: <8902131453.AA04179@sneezy.lanl.gov>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@gauss.llnl.gov.UUCP (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 17

| From: cpw%sneezy@LANL.GOV (C. Philip Wood)
| 
| I vote for something that provides "interoperability".  But,
| interoperability is not the ability of one VMS system to talk to
| another.  The mechanism I would vote for would create an eXternal File
| Representation (XFR), which would allow for REAL "interoperability"
| between HETEROGENEOUS hosts.  It would take care of mapping file
| attributes to and from the file attribute scheme of all time.  And, if a
| mapping was impossible, it would give the phone number of the nearest XYZ
| vendor sales office, so the user could switch to an OS that was flexible
| enough to handle the problem.

  Yech.  Just what we need.  Ftp written by AI people ... :-) Will I have
to have 32Mb of swap space to run ftp now?  Not flaming; just asking that
we don't go over board on this one.

Casey