Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!clyde!cuae2!ihnp4!inuxc!pur-ee!uiucdcs!uiucuxc!hamilton
From: hamilton@uiucuxc.CSO.UIUC.EDU
Newsgroups: comp.sys.amiga
Subject: Re: Problem with Kermit in vt100 v2
Message-ID: <172200002@uiucuxc>
Date: Mon, 17-Nov-86 02:20:00 EST
Article-I.D.: uiucuxc.172200002
Posted: Mon Nov 17 02:20:00 1986
Date-Received: Wed, 19-Nov-86 06:19:58 EST
References: <51@uw-atm.UUCP>
Lines: 26
Nf-ID: #R:uw-atm.UUCP:51:uiucuxc:172200002:000:1378
Nf-From: uiucuxc.CSO.UIUC.EDU!hamilton    Nov 17 01:20:00 1986


james@uw-atm says:
> In article <576@cubsvax.UUCP>, dss@cubsvax.UUCP (David Silver) writes:
> > I found that I couldn't send multiple files by doing a kermit r on
> > a remote machine and kermit send * on the vt100 kermit.  The first file
> > got transfered, the remote kermit went away, and the vt100 kermit sat
> > there trying to send the rest of the files to noone.  Any ideas?
> 
> It went away because it had done what you asked: it had received a single file.
> Kermit had SERVERs added to the protocol to handle just this problem.  They
> allow the remote host to handle multiple transactions with out "intervention"
> for every transaction.  Thus you could send 3 files, receive 1, send 1 more,
> then quit, all this with only one command type to the server.  Of course you
> would be typing the names of several files on the Amiga, but it cann't guess
> the files!

    actually, the kermit protocol itself understands batches; it's not
limited to server mode.  what you need server mode for is the "turnaround":
the switching between sending and receiving without manual intervention.

	wayne hamilton
	U of Il and US Army Corps of Engineers CERL
UUCP:	{ihnp4,pur-ee,convex}!uiucdcs!uiucuxc!hamilton
ARPA:	hamilton%uiucuxc@a.cs.uiuc.edu	USMail:	Box 476, Urbana, IL 61801
CSNET:	hamilton%uiucuxc@uiuc.csnet	Phone:	(217)333-8703
CIS:    [73047,544]			PLink: w hamilton