Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!kazim
From: kazim@Apple.COM (Alex Kazim)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Communications Toolbox questions
Summary: Therein lies the rub
Keywords: Telnet FTP
Message-ID: <37747@apple.Apple.COM>
Date: 10 Jan 90 23:16:18 GMT
References: <9125@hoptoad.uucp> <36869@apple.Apple.COM> <9188@hoptoad.uucp> <37028@apple.Apple.COM> <9223@hoptoad.uucp> <37200@apple.Apple.COM> <9325@hoptoad.uucp> <898@excelan.COM> <5894@internal.Apple.COM> <905@excelan.COM> <1645@intercon.com>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 24

In article <1645@intercon.com> amanda@mermaid.intercon.com (Amanda Walker) writes:
>on the fly has this problem.  This also goes the other way--there are
>terminals (such as the Zenith Z29) that allow you to change the baud rate
>via an escape sequence.  It would be nice if there was a general way for

The problem, though, is that this assumes you're on a connection that under-
stands what a baud rate is.  If you were emulating a Z29 over an ADSP 
connection, baud rate becomes awkward.  What should the ADSP tool do if
someone says: "Baud Rate = 1200"?  And what exactly would the host program
do if its attempt to set the baud rate failed?

The CommToolbox does allow the terminal & file transfer tools to peek at the
connection environment, but setting it is left to the user and the application.
Aside from the engineering issues, the philosophical issue of "Who's in 
Charge' is also present.  

To put your minds at some ease, we are looking into allowing some restricted 
tool to tool communication.  So, if you've got some specific needs, let me know
and we'll see what we can do.

=========================================================================
Alex Kazim, Apple Computer
My Lame Brained Schemes.  I've never even been in a XEROX building
=========================================================================