Attachments
Joon Radley
joon at radleys.co.za
Fri Jul 9 19:56:39 CEST 2004
Hi Bo,
> > The specification only provides for attachments with file names. No
> > provision is made for inline attachments or attachments
> without file names.
> >
> > Should we maybe look at using the Content-ID field of an
> attachment to
> > identify it?
>
> This is more a problem for the attached files than for
> special purpose attachments. For the XML file, the attachment
> mimetype is enough to identify it, and I guess the same could
> be the case for the tnef blob.
>
> The problem is when a user attaches some file to an event -
> then how can we identify the attachment where it's stored in?
> In this case we won't have a mimetype. So instead we just
> search all attachments for one that matches the filename.
>
> Is there any reason to use the Content-ID field instead?
According to the MIME RFC's any mime part ( atttachment ) can look as this:
Content-type: image/jpeg; name="mail.jpg";
Or this:
Content-type: image/jpeg
Both containing exactly the same body.
So we need to specify that when creating a kolab object each attachment must
be assigned a name.
Content-ID idea was due to a lack of sleep. :-)
Best regards
Joon Radley
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joon at radleys.co.za
More information about the format
mailing list