- From: West Suhanic <wsuhanic@acs.ryerson.ca>
- Date: Mon, 27 Nov 1995 15:15:55 -0500 (EST)
- To: Jeffrey Mogul <mogul@pa.dec.com>
- Cc: HTTP working Group <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>
On Mon, 27 Nov 1995, Jeffrey Mogul wrote: > > We've had this discussion at least once before. I firmly believe > that HTTP should NOT be used for real-time continuous media. The > URL mechanism allows us to include multiple transport protocols > (e.g., HTTP, FTP, Gopher) in the web, and if we want to include > real-time continuous, then we should use a protocol optimized for > that. We should not try to turn HTTP into a kitchen-sink protocol, > making it into a second-rate media protocol while also making it > harder to implement. > The media would not have to be served in real-time. Rather I envision the first pass providing the ability to provide users with richer access to media via mechanisms like time code. I don't think including a more media friendly mechansim would make http a kitchen-sink protocol. It could make it more powerful to work with media which would ultimately permit a richer communications environment. - West
Received on Monday, 27 November 1995 12:17:47 UTC