Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.toronto.edu!ietf-nntp-distribution-owner
Message-ID: <0cNX_6W6f095NL0ggR@turbo.bio.net>
Date: Mon, 24 Jun 1991 13:57:26 -0400
From: lear@turbo.bio.net (Eliot)
Original-To: ietf-nntp@turbo.bio.net
Subject: Re: IMAGE {opsys}?
References: <9106240005.AA22646@turbo.bio.net>
References: <9106240005.AA22646@turbo.bio.net>
Newsgroups: list.ietf-nntp
Distribution: list
Sender: list-admin@cs.toronto.edu
Approved: list.ietf-nntp@mail.cs.toronto.edu
Lines:       16

Brian is, of course, correct.  IMAGE and BINARY are two distinct things.
 I was asked by someone else exactly how the two differ.

IMAGE allows for optimizations to occur.  For example, the elimination
of CR/LF conversion.  BINARY is essentially a raw byte copy.  In some
instances the two will have the same results.  However, if a machine
that uses CR/LF as the end of line transmits BINARY to a machine that
uses LF as EOL, the message would not appear as the same information at
the other end.

Another example (only slightly far fetched) would be two systems that
store information in a compressed form.  An appropriate IMAGE mode would
allow them to communicate the compressed information directly without
first converting back.
Eliot Lear
[lear@turbo.bio.net]