home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.misc
- Path: sparky!uunet!digex.com!intercon!udel!bogus.sura.net!howland.reston.ans.net!usc!sdd.hp.com!saimiri.primate.wisc.edu!ames!sgi!steggie!eric
- From: steggie!eric (Eric Fronberg)
- Subject: Compression for the archives ( was: Drive drive)
- Message-ID: <1993Jan27.170859.11489@steggie.mtview.ca.us>
- Sender: eric@steggie.mtview.ca.us
- Reply-To: eric@steggie.mtview.ca.us
- Organization: Mountain View, Ca USA
- References: <!#p30+=@rpi.edu>
- Distribution: usa
- Date: Wed, 27 Jan 1993 17:08:59 GMT
- Lines: 29
-
- 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!" |
- --------------------------------------------------------------
-
-