Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!think!ima!inmet!ada-uts!rouil
From: rouil@ada-uts
Newsgroups: net.news
Subject: Re: Data compression to lower phone
Message-ID: <11400004@ada-uts>
Date: Mon, 9-Jun-86 11:08:00 EDT
Article-I.D.: ada-uts.11400004
Posted: Mon Jun  9 11:08:00 1986
Date-Received: Sun, 15-Jun-86 02:40:54 EDT
References: <2369@phri.UUCP>
Lines: 28
Nf-ID: #R:phri.UUCP:2369:ada-uts:11400004:000:1357
Nf-From: ada-uts!rouil    Jun  9 11:08:00 1986


There are a few problems.  The toughest one is that every article that
passes through here has to get "phri!" prepended to its path line.  No way
to do that without going through the uncompress/compress cycle (at least,
not that I can see).  Pity.
-------------------------
  Unfortunately, I have already missed a good bit of the discussion so if
this is a repeat or just plain wrong, don't flame me.  Constructive
criticism is welcome however.

  In answer to the above problem, would it be possible to compress only
the bodies of the message and leave the path line and any other routing
information uncompressed.  I would think that this would be similiar
to encrypting a message ie. the message is encrypted(compressed) but the
routing information is not.  Some of the problems would be less space/time
saved when the routing info is the majority of the message.  Those annoying
one liners for example.  On messages with "normal" bodies and .sig lines
you would still save space/time on the bodies at least.

On regular messages, just how much space does the routing info take up?

John Rouillard                       ihnp4!inmet!ada-uts!rouil
Intermetrics Inc.
733 Concord Ave
Cambridge, Ma. 02138

Note:  I am not a sys person just an interested user.  The company I work
       would not take responsibility for my existence let alone my opinions