> 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.
I did not address this originally because my original post covered a different
senario. It now seems necessary, because the cost - money cost, for the real
world - of ignoring cached images is too great and because the overhead of
parsing the html files on the server side is also a drawback.
I was trying to get the HTTP spec to look at, but CERN is down (again) and the
HENSA cache doesn't have it, currently. Oh well. I was about to find an unused
character to join the urls with. This is analogous to using + for space when
sending queries with get.
Lets say & is unused. A possible syntax would be
GET multi&url1&url2&url3 HTTP/1.1
A problem I see with this - is there a max line length for a GET command?
Failing which we may be into using POST....
Sorry about the vagueness, folks; I must print out the spec next time it becomes
available.
Chris Lilley
+-----------------------------------------------------------------------------+
| Technical Author, ITTI Computer Graphics and Visualisation Training Project |
+-----------------------------------------------------------------------------+
| Computer Graphics Unit, | Internet: [email protected] |
| Manchester Computing Centre, | Janet: [email protected] |
| Oxford Road, | Voice: +44 61 275 6045 |
| Manchester, UK. M13 9PL | Fax: +44 61 275 6040 |
| <A HREF="http://info.mcc.ac.uk/CGU/staff/lilley/lilley.html">click here</A> |
+-----------------------------------------------------------------------------+