W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 1995

Re: HTTP and Media Serving

From: Gavin Nicol <gtn@ebt.com>
Date: Mon, 27 Nov 1995 09:14:48 -0500
Message-Id: <199511271414.JAA16683@ebt-inc.ebt.com>
To: wsuhanic@acs.ryerson.ca
Cc: sjk@amazon.com, ses@tipper.oit.unc.edu, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
>        Either way there has to be a richer media control mechanism
>        than byte ranges. I think time code is it. For me the important
>        issue becomes which end handles it.

The only problem with having it in the client is that it requires
every client to understand the data format. What happens when a new
data format is invented, or when a client wants frame 1 of an MPEG
movie in GIF form, because it doesn't have the code locally for
handling MPEG?
Received on Monday, 27 November 1995 06:20:39 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:42:56 UTC