Re: HTTP and Media Serving

>        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