At 2:38 PM 10/14/94, Keith Moore wrote:
Content-Type: application/gzip;
uncompressed-type="text/plain; charset=us-ascii"
This scheme does have some drawbacks when compared with a new c-t-e. For
example, it's more difficult to support multipart/alternative properly.
Why so? There's nothing that restricts the encoding which is used for any
of the alternatives (which could be some compression encoding). The
implementation detail of dealing with an encoding over the whole message is
distasteful to contemplate, I agree. But the basic structure of the
headers I don't see as a problem.
john noerenberg
jwn2(_at_)qualcomm(_dot_)com
noerenberg.j (Applelink)
----------------------------------------------------------------------
Don't it always seem to go,
That you don't know what you got til it's gone
Joni Mitchell, "Big Yellow Taxi", 1969
----------------------------------------------------------------------