Subject: | |
From: | |
Reply To: | |
Date: | Sun, 24 May 1998 09:16:50 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Wirt Atmar writes:
>The time has come in the development cycle of QCTerm to seriously begin
>thinking about how file transfer capabilities should be implemented. ...
>appreciated.
>
>At the moment, three different tacks can be imagined. They are:
>
>...
>3. Reverse engineer and use WRQ's PCLINK protocol
>
>This may seem a particularly unsavory approach, but it is almost certainly
>not
>illegal. WRQ has passed out the PCLINK client program freely for many years
>now and has encouraged VARs to do the same.
It might be worthwhile just *asking* for the protocol. It's unlikely that
WRQ will perceive QCTerm as a terribly serious threat to their main
corporate markets, and they might even perceive it as a marketing
opportunity -- giving you the protocol in exchange for an About-box
credit. There's the Old-WRQ protocol as well; it would serve QCTerm's
purposes quite nicely without compromising WRQ's position at all.
There's also:
4. Use an existing file transfer protocol, like ZModem, which already
supports things like checkpoint recovery. ZModem itself would have to be
modified slightly, at least for uploads, to get around the HP3000's
#$**%#! artificial half-duplex limitation, but it's a starting point.
Also, the code is likely to be available already, either in the public
domain or with a licence that fits QCTerm's distribution model.
-- Bruce
--------------------------------------------------------------------------
Bruce Toback Tel: (602) 996-8601| My candle burns at both ends;
OPT, Inc. (800) 858-4507| It will not last the night;
11801 N. Tatum Blvd. Ste. 142 | But ah, my foes, and oh, my friends -
Phoenix AZ 85028 | It gives a lovely light.
btoback AT optc.com | -- Edna St. Vincent Millay
Mail sent to [log in to unmask] will be inspected for a
fee of US$250. Mailing to said address constitutes agreement to
pay, including collection costs.
|
|
|