<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.1">
</HEAD>
<BODY>
Greetings again,<BR>
<BR>
I guess I'll go on record with the BBS "Download" and "Upload" command failures as a bug too.<BR>
On my jnos2.0d the Download command lists the remote file on the terminal, no file is created in the local jnos file directory.<BR>
On my jnos2.0d the Upload command expects the user to enter the file content on the terminal, a file is created on the remote site.<BR>
<BR>
Before this situation is repaired per the documentation, I'd like to pose and alternative action.<BR>
<BR>
Documentation now explains the file will be transferred between jnos nodes, presumably created under the identical name as the source.<BR>
To modify the code to do exactly that could fix the problem.<BR>
But wait...<BR>
<BR>
To modify the documentation to explain that the source or destination is the terminal would also fix the problem.<BR>
I prefer this as step #1 and I will modify both doc and help as needed if our community accepts this approach.<BR>
As step #2 I propose addition of "get" and "put" commands exactly as applied in ftp, and again I will contribute the doc and help changes to support this approach.<BR>
As step #3 other ftp commands might be implemented into the jnos BBS command structure?<BR>
<BR>
As a final thought, file transfer seems to this author to be a worthy capability.<BR>
To implement file transfer under a TCP/IP connection outside the BBS structure that excludes AX.25 file transfer seems flawed.<BR>
OK - that has not been proposed, but I'd like to quash the concept before it surfaces...<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de Skip k8rra k<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>