[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MIME encapsulation of multipart responses
I will ask the same question again so that I hear the answer from those
that think multipart support is NOT necessary in CAP: How do you expect
to deal with ATTACHments and richer content renderings (ie: ALTREPs) if
you do NOT have multipart support in the protocol/engine? (Will they
magically appear in my local CUA or will it have to download them using
some undocumented CAP command or OOB mechanism??)
I must admit, that because there was nothing about this in the draft, I assumed that the CS just
stored URIs or encoded attachments. But I did forget about ALTREP.
But I still don't think multipart it the way to go.
If we allow multipart/related with URIs pointing to attachments, then how do we get the data back
out of the CS. If I do a search, then I just get objects and properties.
Either we need some commands for storing and retrieving attachments in the CS, or we change search
to return multipart/related.
I would prefer some new commands and stick to text/icalendar as our command format.