HP3000-L Archives

May 1998, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bill Lancaster <[log in to unmask]>
Reply To:
Bill Lancaster <[log in to unmask]>
Date:
Sat, 23 May 1998 21:44:01 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
At 02:56 PM 5/23/98 EDT, WirtAtmar wrote:
>At the moment, three different tacks can be imagined. They are:
>
>1. Use a QCTerm-specific file transfer protocol
>

<snip>

>
>2. Use FTP
>

<snip>

>
>3. Reverse engineer and use WRQ's PCLINK protocol
>

<snip again>

It seems to me that a philosophy of "the greatest good for the greatest
number" would be a good starting point.  To that end, I suggest that you
implement FTP first, and then, if or when, time permits, consider how to
address your classic constituency.

Maybe you can cross-license some file transfer technology (but I suggest
you don't call Minisoft :-)

Have you spec'ed what it would take to create your own file transfer
capability?  Even if it isn't daunting, you would still be left with the
"how to get the file transfer program to the 3000" problem.  Using FTP
eliminates that problem for many possible QCTerm users.


Bill Lancaster

ATOM RSS1 RSS2