Re: HTML Streaming

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


Date: 27 Aug 1997 17:09:00 +0100
From: Peter Flynn <pflynn@imbolc.ucc.ie>
To: Albertfine@aol.com
Cc: www-html@w3.org
Message-id: <199708271609.RAA27588@imbolc.ucc.ie>
Subject: Re: HTML Streaming

> This "sloppy behavior" makes HTML very easy to write. I think this is one of 
> the reasons why the web is so popular. It also allows experienced HTML 
> coders to write very lean code.

Yes...it will also make it virtually impossible for such pages ever 
to upgraded to XML on an automated basis, or reused in any other SGML 
system. That's fine for a lot of people, but not so fine for others.

> You can stream a wav file if you wanted to but it would sound pretty bad.
> RAM files are designed to be streamed and they sound pretty good. HTML is 
> streamed yet it is not designed to be streamed. I want HTML protocols that 
> allow them to be streamed.

I still don't see what you want changed in HTML and why it would make
it better for streaming.

> It is something people care about. It cannot be done by the browser alone. 
> Like Real Audio, streaming a file is not a matter of servers or viewers. It 
> is really a matter of the file format and sample rate; the HTML analogous
> being the organization of tags and the protocols for HTML editors.

Ah, so it's not really the element order you're worried about, it's the
synchronization of the arrival. OK, so add some HyTime smarts to HTML.

> I think all tags should be reviewed and changed to make them streamable. 

Fine, but it wouldn't then be HTML, it would be something different.

> course, this is a very big step. I think the first step should be the 
> organization of tags and review of the some of more experimental and 
> proprietary additions to HTML files.

Such as? Have you got examples of what you want to do?

///Peter