Re: HTTP and Media Serving

• From: West Suhanic <wsuhanic@acs.ryerson.ca>
• Date: Mon, 27 Nov 1995 01:58:04 -0500 (EST)
• To: Gavin Nicol <gtn@ebt.com>
• Cc: sjk@amazon.com, ses@tipper.oit.unc.edu, HTTP working Group <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>
• Message-Id: <Pine.A32.3.91.951127015207.155438B-100000@hopper.acs.ryerson.ca>

Hi Again:

	I think the central issue here is where the concept of media
	is handled. If the HTTP server is considered as a media server
	then it must have the facilities to deal with media. Time code
	is the language of the professional media creators. Therefore 
	given the web's ever increasing consumption of media it would
	have to deal with time code. However if the server is still
	viewed as a byte stream server then this would push the
	responsibilty for dealing with  media out to the clients; ie,
	browsers and any tools they use.

	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.

Received on Sunday, 26 November 1995 22:58:46 UTC