Xref: utzoo comp.mail.misc:5482 comp.mail.uucp:6567 Newsgroups: comp.mail.misc,comp.mail.uucp Path: utzoo!utgpu!cunews!micor!latour!mcr From: mcr@Sandelman.OCUnix.on.ca (Michael Richardson) Subject: Re: BITFTP grief! Message-ID: <1991May19.190054.3305@Sandelman.OCUnix.on.ca> Organization: Sandelman Software Works, Debugging Department, Ottawa, ON References: <1991May16.145758.6817@uu.psi.com> <1991May17.202220.9531@uu.psi.com> Distribution: na Date: Sun, 19 May 1991 19:00:54 GMT In article <1991May17.202220.9531@uu.psi.com> schoff@uu.psi.com (Martin Schoffstall) writes: >But lets go back to your rftp, what you need to do is create the >code and make it work across 2 dozen platforms and it will be >as explosive as CNews use. So get the community to work the >spec and write the code and we're off, minimum portability would be >bsd4.x >sunos >sysv >xenix >ice's Uaccess >uupc >aix Why? All the meat is on the server (your box) not the customers. You simply 'uuto' it to them once it is there. Are you saying that you run such a wide spread of access machines? (UUPC??) You may want to chop large files into smaller (binary) files, and this may require some thought as to the correct format to pick (and how to verify integrity of each part), but would be an enhancement so that 2meg tar.Z files can still be sent over a line which only stays up for an hour at a time... >Your biggest and most controversial design decision will be to >decide if this works one hop or multiple hops. Does uucp/uuto? Does uux? -- :!mcr!: | The postmaster never | So much mail, Michael Richardson | resolves twice. | so little time. HOME: mcr@sandelman.ocunix.on.ca Bell: (613) 237-5629 Small Ottawa nodes contact me about joining ocunix.on.ca!