Re: HTTP-NG: status report

Brian Behlendorf (
Tue, 22 Nov 1994 10:27:36 +0100

Looked great!

The act of fetching inlined images could be made faster if the server
were able to tell the client directly in its response headers "I think
you'll want to get these items next" - that way the client doesn't have
to parse the document as it's coming down the pipe looking for inlined
images. I.e., in HTTP/1.0 terms (since I haven't seen the HTTP-NG terms)

C: GET / HTTP/1.0

S: ...
Inlined-objects-URI: /Images/yes.gif, /Images/no.gif

The server just has to spend the effort to derive this info once and can
cache it in memory or to disk from then on, doing quick if-modified
checks to see if that info may have changed. The client then still has
the option of getting the inlined object from a cache somewhere.


Your slick hype/tripe/wipedisk/zipped/zippy/whine/online/sign.on.the.ish/oil
pill/roadkill/grease.slick/neat.trick is great for what it is. -- Wired Fan #3