The idea that some of us came up with was to add a parameter for all types
called something like "disposition" that would indicate if it should be
displayed in full or as an attachment. The good thing about this is that
it is easy to implement and it works for all the types. There's no
overloading some more meaning on to some types. For example deciding that
text parts should always be displayed. This way you also keep the type
info for each attachment (Image/GIF, App/PostScript...). This is important
at least in the case of text versus binary data to know when to convert to
the local new line convention.
LL
On Mon, 1 Mar 1993, Bill Janssen wrote:
The real issue here seems to me to be ``which of the bodyparts is the
non-attachment?'' I think there's a real need to have another multipart
subtype, namely ``attachments'', in which all bodyparts except for the
last are treated as attachments to the last part, which is treated as
the ``main'' message. This eliminates the need for adding any headers
to the bodypart.
Bill