🚀 go-pugleaf

In article <780079@hpvcfs1.HP.COM> mikek@hpvcfs1.HP.COM (Mike Kirkpatrick) writes:
>
>Compuserve B file transfer protocol just dropped off the face of the earth.
>There was absolutely NO mention of it in the manual. Scott, when you make 
>such significant changes from one rev to another, don't you think it at least
>deserves a mention in the manual. There should be a chapter way up front in
>the manual devoted to major changes from previous rev like this. The example
>dialog with Compuserve you have in the manual uses XMODEM protocol. Is this
>the best choice, and won't this require more user interaction for downloading?
>XMODEM does not send the file name at the beginning of the transfer acording
>to your description of transfer protocols. What is the history of Compuserve B
>and the new derivatives now available on Compuserve? I thought you were the 
>one who invented it. Why abandon it now?
>
     Errr, not quite...  CompuServe B has been removed from the program itself,
but there's an RCMD (documented on p.253) that implements Quick B protocol.
As long as CompuServe offers the faster QuickB now, there doesn't seem to me
to be much point in implementing the original CompuServe B.
     The only restriction I can see is that this would make it difficult or
impossible to use B/Quick B in your own procedures (since the QuickB RCMD is a
procedure itself)... of course, I've never actually used the RCMDs yet myself
(since I've had Internet access, I haven't felt the need for CI$... :) ),
so I could be wrong about this.  (When I actually get a Mac, I imagine I'll
become somewhat more familiar with WK... ;) )


-- 
Internet: phaedrus@blake.acs.washington.edu    (Univ. of Washington, Seattle)
  The views expressed here are not those of this station or its management.
   "If you can keep your head while those about you are losing theirs,
      consider an exciting career as a guillotine operator!"