home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
archives
/
protocol.zip
/
whatami-jrd.msg
< prev
next >
Wrap
Text File
|
1994-06-09
|
1KB
|
30 lines
9-Jun-94 2:27:41-GMT,1263;000000000005
Received: from grumpy.usu.edu by watsun.cc.columbia.edu with SMTP id AA13478
(5.65c+CU/IDA-1.4.4/HLK for <fdc@watsun.cc.columbia.edu>); Wed, 8 Jun 1994 22:27:40 -0400
Received: from cc.usu.edu by cc.usu.edu (PMDF V4.2-13 #4757) id
<01HDB90YW7KGC2JFP3@cc.usu.edu>; Wed, 8 Jun 1994 20:27:30 MDT
Date: Wed, 08 Jun 1994 20:27:30 -0600 (MDT)
From: Joe Doupnik <JRD@cc.usu.edu>
Subject: Whatami
To: fdc@watsun.cc.columbia.edu
Message-Id: <01HDB90YW9GIC2JFP3@cc.usu.edu>
X-Vms-To: IN%"fdc@watsun.cc.columbia.edu"
X-Vms-Cc: JRD
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Frank,
Oh yes, there is one aspect of this not covered. That is, a smart
client and a less smart server. The user won't know and may think the
server is smart. We may have to provide a message that the server won't
track the client, as say part of the I/Y packet exchange.
"Notice that the remote server does not follow local settings
for binary and text file transfers, please use the command REMOTE SET FILE
TYPE BINARY or TEXT to have the server send files in the desired manner."
Or better words of that kind. And I'm anticipating a Nag ON/OFF
switch to be requested.
Now to add the few lines of code to activate the mechanism.
Joe D.