Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site watcgl.UUCP
Path: utzoo!watmath!watcgl!dmmartindale
From: dmmartindale@watcgl.UUCP (Dave Martindale)
Newsgroups: net.bugs.uucp
Subject: Re: uucp vs. sytek (and switches in general)
Message-ID: <2402@watcgl.UUCP>
Date: Wed, 11-Apr-84 12:53:13 EST
Article-I.D.: watcgl.2402
Posted: Wed Apr 11 12:53:13 1984
Date-Received: Thu, 12-Apr-84 05:26:21 EST
References: <126@down.UUCP>
Organization: U of Waterloo, Ontario
Lines: 12

Unless you are using "hardware" flow control on both hosts talking via
Sytek, you have to use XON/XOFF (and probably TANDEM mode) to do flow
control.  Thus you need a new protocol that doesn't transmit XON, XOFF,
or those characters with the parity bit set.  While you're at it, you might
as well eliminate the character which introduces the box's command sequence,
so you don't have to disable that.

A busy SYTEK channel can get slow enough that trying to do this without
flow control, using timeouts to pick up messages garbled by overruns,
could really slow things to a crawl.  And if you don't have the command
sequence on the box disabled and transmit the characters which put the
box into command mode, you've just hung the connection completely.