Re: revised MIME architecture

Dan Connolly <>
Message-id: <>
To: (Jean Francois Groff)
Subject: Re: revised MIME architecture 
In-reply-to: Your message of "Mon, 08 Jun 92 00:41:18 +0200."
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=cut-here
Date: Sun, 07 Jun 92 22:37:29 CDT
From: Dan Connolly <>


>	Dan,
>  OOPS... You sent this one to www-interest instead of www-talk...
>I'm getting ready for some flamage from clueless list members :-)
Did I? I sent several messages, and I though I was careful to
send them all to www-talk. Oh well... Sorry!

>  Regarding your proposal, the idea is exciting, although I find it
>annoying that small documents, like most HTML pages are, will suddenly
>take 4 times as much storage and bandwidth due to verbosity.
They won't necessarily take 4 times as much storage: the verbose part
_could_ be generated on the fly. by the server.

On the other hand, it _is_ simpler to store things in the format that
they'll be used. This brings up the issue of authoring documents in
this format. I'm developing some ideas on interactive composition
of MIME messages (using EMACS, FrameMaker, or perhaps a Tk application)
but for now, it's somewhat tedious.

>  I'd like to develop on this, but I lack MIME background and, believe
>it or not, I couldn't find the MIME RFC in the archive indexes ; could
>you tell me (and the list) its number? Also, pointers to existing MIME
>readers would be welcome.
I've gotten several "nifty... so what is MIME?" responses. So I'll
tell you what I told them...


>Where can I get more information about MIME?
>			Thanks.

The author of the rfc is Nathaniel Borenstein <>.
Most of the publicly available material is on in

Content-Description: RFC-XXXX (MIME)
Content-Type: multipart/alternative; boundary=alt

Content-Type: message/external-body;

Content-Type: text/plain

Content-Type: message/external-body;

Content-Type: application/postscript