Article View: comp.mail.mime
Article #65re: Table of contents for a MIME note?
From: Mark Crispin
Date: Wed, 27 Jan 1993 10:12
Date: Wed, 27 Jan 1993 10:12
13 lines
1438 bytes
1438 bytes
IMAP2bis solves the problem by extending IMAP2 to transmit the MIME structure of messages. So, for remote mailboxes, you don't need to fetch the entire text of the message just to get its MIME structure. This was one of the things that caused a long debate in the MIME working group, with me having to fight tooth and nail to make sure that MIME didn't do things that would make the determination of MIME structure difficult (e.g. the prohibition of recursive encoding is due to my insistance). I don't think that having a separate structure index in the message itself is a good idea, because that introduces a new failure mode in which the actual message structure doesn't correspond to its index. We're all better off making sure that it continued to be easy to parse MIME quickly.
Technical Details
Message-ID:
<MS-C.728187159.377401575.mrc@Tomobiki-Cho.CAC.Washington.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!ogicse!news.u.washington.edu!news.u.washington.edu!newsShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!ogicse!news.u.washington.edu!news.u.washington.edu!news From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) Newsgroups: comp.mail.mime Subject: re: Table of contents for a MIME note? Message-ID: <MS-C.728187159.377401575.mrc@Tomobiki-Cho.CAC.Washington.EDU> Date: 27 Jan 93 10:12:39 GMT Article-I.D.: Tomobiki.MS-C.728187159.377401575.mrc Organization: University of Washington Lines: 13 NNTP-Posting-Host: tomobiki-cho.cac.washington.edu To: William Chung <whchung@watson.ibm.com> In-Reply-To: <1993Jan27.164758.15466@watson.ibm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII