Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC840302); site mcvax.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!piet
From: piet@mcvax.UUCP (Piet Beertema)
Newsgroups: net.dcom
Subject: Re: uucp and Tymnet
Message-ID: <816@mcvax.UUCP>
Date: Mon, 7-Oct-85 07:40:03 EDT
Article-I.D.: mcvax.816
Posted: Mon Oct  7 07:40:03 1985
Date-Received: Wed, 9-Oct-85 06:34:15 EDT
References: <11886@rochester.UUCP> <11200002@uiucuxc>
Reply-To: piet@mcvax.UUCP (Piet Beertema)
Organization: CWI, Amsterdam
Lines: 19


	....in my case, i modified the stuffing to leave "benign" control chars
	(newline, tab, etc) alone; my problem was with ^S/^Q and anything >= 0200.
	the actual protocol is still "g" (renamed "h"), so you still get per-packet
	acks and checksums. thruput isn't too bad
As expected, on a local net. But don't try to use it over international X.25/PAD
links: the throughput will go way down, the bills way up...

	...if the pk1.c code does reads and writes of whole packets (i never really
	deciphered it), you could add an end-of-message character to each packet to
	avoid waiting for timeout
That's the approach I took before writing the f-proto. It worked, but still was too
slow because of the ack packets, and expensive: the g-proto writes 64 bytes + header
(6 bytes), which is 2 (64-byte) segments, the X.25 accounting unit; the ack packet
is another segment; so you pay for three segments to get one across.....

-- 
	Piet Beertema, CWI, Amsterdam
	(piet@mcvax.UUCP)