--On Thursday, March 20, 2003 10:12 PM +0200 Timo Sirainen <[EMAIL PROTECTED]> wrote:
|> I claim issue 1 is actually a non-issue. Update non-aware clients are |> allowed to continue on in blissful ignorance. | | No, that won't work. Clients may have cached only parts of the message. | Now what happens if you modify the message, but client has it partially | cached and tries to fetch the rest of it? Trying to continue partial | body[] fetch could give you completely corrupted message.
One of the more common requests I get as a client vendor is for users to have the ability to delete attachments on the server. Obviously that can be done via FETCH/modify in client/APPEND/EXPUNGE, but an in-place solution would be preferred.
My solution (which I'm not really proposing as I don't think anyone wants to break immutable messages) is to simply set the body part content to zero for the attachment being deleted and add a 'Content-Disposition: removed' header for that part. The only clients that are going to have an issue with this are those that have cached the MIME part size for that attachment. The actual MIME structure is not affected - the use is left with a 'tombstone' to show that the message did contain a part in the past.
-- Cyrus Daboo
