Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.toronto.edu!ietf-nntp-distribution-owner
Message-ID: <9106250011.AA25533@tmc.edu>
From: sob@tmc.edu (Stan Barber)
Date: Mon, 24 Jun 1991 20:11:57 -0400
References: lear@turbo.bio.net (Eliot)
       "compression methods" (Jun 24,  4: 23pm)
X-Mailer: Mail User's Shell (7.1.1 5/02/90)
Original-To: lear@turbo.bio.net (Eliot)
Subject: Re: compression methods
Original-Cc: ietf-nntp@turbo.bio.net
Newsgroups: list.ietf-nntp
Distribution: list
Sender: list-admin@cs.toronto.edu
Approved: list.ietf-nntp@mail.cs.toronto.edu
Lines:       12

Why build compression in? Why not just use the same mechanism uucp/batching
uses now? Adding compression adds ALOT of overhead. Using image/binary and
the existing news batching adds very little.

If the goal it to make low speed lines usable (say over a NetBlazer)
with NNTP for TRANSMISSION (not READING), compression in nntp is not necessary.


-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: rutgers!bcm!sob             and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine