Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!decwrl!pyramid!csg
From: csg@pyramid.pyramid.com (Carl S. Gutekunst)
Newsgroups: comp.mail.uucp
Subject: Re: UUCP Over TCP/IP (why?)
Message-ID: <33882@pyramid.pyramid.com>
Date: 3 Aug 88 02:09:41 GMT
References: <4644@b-tech.UUCP> <413@comdesign.UUCP> <4648@b-tech.UUCP>
Reply-To: csg@pyramid.UUCP (Carl S. Gutekunst)
Organization: Pyramid Technology Corp., Mountain View, CA
Lines: 15

In article <4648@b-tech.UUCP> zeeff@b-tech.UUCP (Jon Zeeff) writes:
>I've been running a comp.* news feed over dial-up lines with 'f' for 
>several months without problems.

That's an expensive way to run a news feed. Being 7-bit, the 'f' protocol
exacts a 40% overhead penalty on binary files (like compress output). The 'g'
protocol is full 8-bit, so have only the usual 8% packetizing overhead. You
can use the ~news/encode filter, but that's still a 19% overhead.

>It should also work well with an error-free modem (like a Trailblazer).

Prior to Telebit's firmware rev 3.0, it was the *only* way to talk UUCP over
a TrailBlazer. It worked well enough that we still use it for some links, if
we aren't trying to pass news.

<csg>