Re: HTML Streaming

Peter Flynn (pflynn@imbolc.ucc.ie)
27 Aug 1997 00:40:00 +0100


Date: 27 Aug 1997 00:40:00 +0100
From: Peter Flynn <pflynn@imbolc.ucc.ie>
In-reply-to: <970825092650_465514055@emout06.mail.aol.com> (Albertfine@aol.com)
To: Albertfine@aol.com
Cc: www-html@w3.org, jptxs@idt.net
Message-id: <199708262340.AAA22311@imbolc.ucc.ie>
Subject: Re: HTML Streaming

Albert Fine writes:
   You give the problem very little credit. MSIE actually got press
   for displaying an image less version of the HTMl file first. The
   time it takes to display a HTML file is a factor especially with
   ever increasing connection speeds. Their has been little effort on
   the part of file format protocols to have what is displayed sent
   first.

Ahhh. You mean you want the client/server protocol of the Web to 
alter the document structure according to the perceived content?

Most HTML files are tiny compared with the graphics they reference.
The text content therefore _does_ get sent first...but the browsers
are delaying its display until the graphics can be located wrt size
and shape.

   The title tag is a very simple example. A good way to look at this
   is "what is displayed, send first. What is not displayed, stick at
   the bottom." I also have several specifications to give more
   control over how and when the browser displays the HTML
   file. Again, this is still very early in development.

I think you have seriously misunderstood the reason for the TITLE
element. It's not there in order not to be displayed; it's there to
identify the file, and I think you'll find that its contents appears
in the titlebar of most browsers almost immediately file reception
starts, which completely negates your point.

But I'd be interested to know what else you'd like added to control
the browser's behavior.

///Peter