Xref: utzoo comp.mail.misc:5452 comp.mail.uucp:6519 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!princeton!njin!uupsi!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.mail.misc,comp.mail.uucp Subject: Re: BITFTP grief! Message-ID: Date: 17 May 91 18:32:25 GMT References: <81678@bu.edu> <1705@aupair.cs.athabascau.ca> <1991May16.145758.6817@uu.psi.com> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Distribution: na Organization: Xenix Support, FICC Lines: 24 In article <1991May16.145758.6817@uu.psi.com> schoff@uu.psi.com (Martin Schoffstall) writes: > Mailing files is one of those things that doesn't work very reliably, Why does remote ftp have to have anything to do with mail? An interface like this would be great for those of us with no SLIP capability: "uux uupsi!rftp sprite.berkeley.edu:~ftp/mx.tar.Z (ficc!~/from-uupsi)" I realise this might hurt your flat rate pricing, so you could restrict rftp to people with DCS or LAN-DCS access, or impose a surcharge, or something. UUNET would be able to do this without pain. And it would strongly discourage people from using mail for file transfer. > To transfer files we use a tried and true mechanism: FTP. Which requires interactive access to the Internet. When one is using an intermittent transport mechanism (dial-ups and modems) a store-and-forward technique is much more useful. With a smart enough UUCP on your end, you could even avoid staging the file at all in most cases. -- Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180; Sugar Land, TX 77487-5012; `-_-' "Have you hugged your wolf, today?"