Re: Multipart/mixed for many inline images (was Re: Toward Closure on HTML)
wmperry@indiana.edu (William M. Perry)
Errors-To: listmaster@www0.cern.ch
Date: Fri, 8 Apr 1994 20:57:42 --100
Message-id: <m0ppKjg-00002BC@monolith>
Errors-To: listmaster@www0.cern.ch
Reply-To: wmperry@indiana.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: wmperry@indiana.edu (William M. Perry)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Multipart/mixed for many inline images (was Re: Toward Closure on HTML)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 853
How should/would one send the multiple requests? It would not be feasible
to say GET url1 url2 url3, as this would interfere with GET url HTTP/1.0.
Perhaps an X-header?
I don't think we should go so far as to have a new method just for
retrieving multipart messages.
As for the returned message, how about something like this to send foo.gif,
bar.xbm, and baz.xpm?
HTTP/1.0 200 OK
Date: Friday, 08-Apr-94 18:47:32 GMT
Server: NCSA/1.1
MIME-version: 1.0
Content-type: multipart/mixed; separator=--foo
Last-modified: Thursday, 31-Mar-94 16:16:57 GMT
--foo
Content-type: image/gif
Content-id: foo.gif
Content-length: xxxx
[image data]
--foo
Content-type: image/x-xbitmap
Content-id: bar.xbm
Content-length: xxxxx
[image data]
--foo
Content-type: image/x-xpixmap
Content-id: baz.xpm
Content-length: xxxx
[image data]
[close connection]
-Bill P.