On Mon, Apr 1, 2013 at 4:29 AM, Kumar McMillan <[email protected]>wrote:
> On Saturday, March 30, 2013 2:31:23 PM UTC-5, Robert O'Callahan wrote: > > But I think we should fix that if we can come up with a good enough > > > > heuristic for determining whether a stream is live. > > I think coming up with an heuristic would be hard. Servers like Live365 > are notorious for using dumb headers (like content-length: 2000000, wat?) > > > Otherwise maybe we should add an attribute to indicate liveness. > > This sounds like the best solution to me. It's a common use case to open a > live streaming URL and the developer is in a good position to make that > decision. > But if the developer is sending dumb headers, how can they be trusted to use the liveness attribute correctly? Would it be reasonable to say that we should treat an HTTP resource as live if and only if it has no Content-Length? And then try to get providers who are sending bogus Content-Length to stop sending Content-Length? Rob -- q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
