Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!excelan!brianb
From: brianb@kinetics.com (Brian Bulkowski)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Communications Toolbox questions
Message-ID: <872@excelan.COM>
Date: 12 Dec 89 20:38:38 GMT
References: <9125@hoptoad.uucp> <36869@apple.Apple.COM> <9188@hoptoad.uucp> <37028@apple.Apple.COM> <9223@hoptoad.uucp>
Sender: news@excelan.COM
Reply-To: brianb@plasma.UUCP (Brian Bulkowski)
Organization: Kinetics, A Novell Co.
Lines: 29

In article <9223@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>
>I don't understand the relevance of that last comment.  The issue is not
>alternate XMODEM implementations, but implementations of other file
>transfer protocols, like FTP, ZMODEM, and so forth.
>
>While we're on the subject, can you briefly sketch how an FTP protocol
>tool could be created under the Communications Toolbox?
>

Boy, wouldn't I like to know that too! What I'd like out of the CommTB
is a generic file transfer method. For me, file transfer is broken into
(at least) these parts:
1) query list of host files.
2) query list of local files.
3) get host files.
4) put local files.
5) make directories in both file structures.
6) move around in both file structures.
7) Encode or decode various file formats (XMODEM, MacBinary, ... )

I was hoping that that's what a file transfer tool would do all of these
things independantly. Thus I could use my FTP interface (boy, do I like it)
over LU6.2. Or FTAM. Or AFP.

Is this possible? Reasonable?

Brian Bulkowski
Software-type-person