Excerpts from mail: 22-Nov-94 Re: HTML in MIME mail
Harald(_dot_)T(_dot_)Alvestrand(_at_)unin (460)
On the other hand, if I have a MIME HTML message where the first part is
text/html with reference to part 2, for instance "here are the <a....>
financial reports</a> for this quarter", and then copy the first body
part to a new message for the next quarter, I want the reference to be
to *this* message's body part 2, not the previous quarter's.
Interesting. I was thinking about references to stable entities, and
you're pointing out references to dynamic ones. Both must be supported,
I agree.
But it isn't clear to me that this argues for reference by part number.
Changing a part inside a multipart is not, in general, as trivial as
updating a file, which is how dynamic entities are handled on the web
today. If you're changing a component of a multipart, how much trouble
is it to preserve the old Content-ID if you want a dynamic entity?
Probably not much. But now this seems to violate the meaning of
Content-ID, doesn't it?
Agree that this needs a bit of thinking about! Now to find someone
to do the thinking....
Yes, that's the problem alright. I suspect we'll end up with two rather
different schemes for referencing stable and dynamic entities. --
Nathaniel