Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!intercon!amanda@mermaid.intercon.com
From: amanda@mermaid.intercon.com (Amanda Walker)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Communications Toolbox questions
Message-ID: <1621@intercon.com>
Date: 13 Dec 89 16:10:41 GMT
References: <9125@hoptoad.uucp> <36869@apple.Apple.COM> <9188@hoptoad.uucp> <37028@apple.Apple.COM> <9223@hoptoad.uucp> <37200@apple.Apple.COM>
Sender: news@intercon.com
Reply-To: amanda@mermaid.intercon.com (Amanda Walker)
Lines: 23

In article <37200@apple.Apple.COM>, austing@Apple.COM (Glenn L. Austin) writes:
> First, FTP requires its own connection.  This can be handled, since a hypo-
> thetical FTP FT tool would have the "ftSameCircuit" bit clear, which tells the
> application to create a new connection for the file transfer.  Once that is
> done, the FT tool is free to use the circuit as they please.  The only "magic"
> is that the file transfer actually occurs asynchronously, rather than "start
> transfer, return when complete."

The only way I see to write an FTP tool currently is to have the file transfer
tool talk to MacTCP directly, bypassing the (hypothetical) Telnet tool
completely.  FTP requires two separate connections, one of which could be
done with a Telnet connection (the command channel), but one of which is
most definitely not a terminal-style connection of any sort (the data channel).

The Comm Toolbox looks like a marvelous effort, but its metaphors seem to
break down more and more the farther your get from a serial line...

Disclaimer: I haven't actually tried writing an FTP transfer tool yet, so
I may well be just confused.

Amanda Walker
InterCon Systems Corporation
--