Article View: comp.sys.next.misc
Article #4751Re: Compression for the archives (and FTP enhancements)
From: Gregor Purdy
Date: Wed, 27 Jan 1993 20:47
Date: Wed, 27 Jan 1993 20:47
11 lines
1166 bytes
1166 bytes
You could have the ftp client on the user's side to all the compression and decompression. Thereby, the uncompressed version would never be sent over the net. You could even build a version of an ftp client that looked at the filename extensions on the files it was transferring and either automatically decompress or prompt the user for permission to decompress (a preference). Then, you could configure it to do any compression/decompression scheme you wanted by having it do call outs to filter programs. You'd just need a way to associate an extension with a filter program... --Gregor N. Purdy Contemporary Design Studios
Technical Details
Message-ID:
<1k6scpINNkdt@terminator.rs.itd.umich.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!europa.eng.gtefsd.com!emory!sol.ctr.columbia.edu!destroyer!news.itd.umich.edu!news.itd.umich.edu!usenetReferences:
<1k6q1eINNqai@shelley.u.washington.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!europa.eng.gtefsd.com!emory!sol.ctr.columbia.edu!destroyer!news.itd.umich.edu!news.itd.umich.edu!usenet From: gregor@oit.itd.umich.edu (Gregor Purdy) Newsgroups: comp.sys.next.misc Subject: Re: Compression for the archives (and FTP enhancements) Date: 27 Jan 1993 20:47:21 GMT Organization: University of Michigan Lines: 11 Distribution: usa Message-ID: <1k6scpINNkdt@terminator.rs.itd.umich.edu> References: <1k6q1eINNqai@shelley.u.washington.edu> NNTP-Posting-Host: fredrik.oit.itd.umich.edu