--- Begin Message ---
The last paragraph of section 7.2.3 recommends the use of the same content-id
for each of te alternative parts in a multipart/alternative entity. I
understand the reasoning behind this but am having a hard time figuring out the
ramifications vis-a-vis message/external-body use of content-id. Take the
following example:
content-type:multipart/alternative;boundary=alt
--alt
content-type:message/external-body;access-type:ftp ...
content-id: shared-id
content-type:image/xbm
content-description: black and white version of mockup of new machine, to be
shown on a black and white display
--alt
content-type:message/external-body;access-type:ftp ...
content-id: shared-id
content-type:image/gif
content-description: nice colorful version of mockup of new machine, to be
shown
on a color display
--alt--
Lets say I've got a networked home directory across my work and home
environments. At home I've got a 1 plane display and at work a color display.
I
read the message at home and my UA acesses the xbm version and caches it using
the "shared-id" content-id. The next day I reread the message at work and
can't
get at the color image due to the caching. If the content-id for
message/external-body were associated with the encapsulated headers there
wouldn't be a problem, but as it stands there is a conflict between the use of
content-id in multipart/alternative and message/external-body.
Gabe
--
Gabe Beged-Dov e-mail: gabe(_at_)cv(_dot_)hp(_dot_)com
Hewlett-Packard
Open Systems Software Division,
Corvallis, Oregon phone: (503)750-4415
--- End Message ---