lilley@v5.cgu.mcc.ac.uk (Chris Lilley, Computer Graphics Unit) writes:
> Case 1: client has inline images ON and supports multipart messages, server is
> multipart aware
> Server bundles up blah.html and all its inline images as a MIME multipart, ships
> it all over the net in one go, client unpacks it and does the right things with
> the bits.
What if the server already happens to have some of the images cached?
It seems like a waste to be constantly retransmitting the images.
> Case 2: client has inline images OFF and supports multipart messages, server is
> multipart aware
>
> Server sends blah.html as current situation
Presumably with links of some sort, so that the images could be
fetched later. (heh. Using 'message/external-body' as a base, define
content-type 'image/external-body'... :-)
I still think that the current scheme of embedding URL's to images in
lieu of the images is a good one. Granted, the need to reconnect for
every image is annoying; it would be "nice" to be able to send multiple
requests per connection to servers that didn't immediately close down...
)Rob