🚀 go-pugleaf

I've been watching from afar the discussions of Disk space vs a  new
compression technique used on the NeXT archives and wanted add some
input of how to deal with additional compression on the archives.  

The source of FTP is generally available.   Why not modify FTP do all
the compressing/uncompressing on the users behalf.  Any worthwhile
compression scheme could be used (zip, gzip, perhaps even a command
line version of squash, if it exists)  

A person submitting a file would just ftp it to an archive sight and
ftp would pipe the file through some compression algorithm and onto
the disk.  Likewise when one extracts a file from the archive the
file is decompressed (if it was compressed in the first place) and 
given to the user. 

This way the people submitting and the people retrieving data need 
never concern themselves with how the data is stored just that it's 
accessible.


-- eric


--------------------------------------------------------------
| Eric Fronberg    |  email: eric@steggie.mtview.ca.us       |
| Mountain View CA |        ...!{sun,sgi,ultra}!steggie!eric |
| 415 967-2748     |  vmail: "Hey, you!"                     |
--------------------------------------------------------------