- From: <Albertfine@aol.com>
- Date: Wed, 27 Aug 1997 19:29:26 -0400 (EDT)
- To: www-html@w3.org
Members of the www.html List, I think I see a flame war simmering so let me make a few things clear. I don't work for Double Click :) I am a computer consultant. I have taken classes on HTML and I have reviewed the XML and HTML 4.0 specifications. I am sure everyone here knows something about HTML. My ideas are very early in development. HTML streaming basically; organizes the tags in a HTML document to send what is displayed first. Tags that are not displayed such as keywords, signatures etc. would be added at the end of the file. These protocols would probably be used by HTML editors. HTML streaming also involves two tags; the events tag and the stream tag. The event tag would list all the tags in the HTML file with rough descriptions so the browser knows what to expect. The stream tag would tell the browser you can display this now, it will not be changed. For example, someone mentioned the problem with loading tables. The HTML editor could calculate the impact of size elements in the table tag. It would add a stream tag to points in the table. The stream tag would tell the browser to display the unfinished table knowing that it will not be changed. Or the HTML editor could add a rough description of the table to the events tag. You would have the table streamed without major changes to the table tag or using a proprietary tag. I don't think tables are the last or only example of the need for HTML streaming. I don't think the speed at which a page loads while downloading is the biggest problem in the world but I do think we should take the initiative. Please review all the articles in the thread; http://lists.w3.org/Archives/Public/www-html/1997Aug/thread.html#290 Albert Fine
Received on Wednesday, 27 August 1997 19:29:29 UTC