[FFmpeg-devel] [PATCH 2/7] avio: deprecate url_is_streamed

Ronald S. Bultje rsbultje
Fri Mar 11 13:31:11 CET 2011


On Fri, Mar 11, 2011 at 3:43 AM, Tomas H?rdin <tomas.hardin at codemill.se> wrote:
> Michael Niedermayer skrev 2011-03-08 12:28:
>> On Mon, Mar 07, 2011 at 10:24:21AM -0500, Ronald S. Bultje wrote:
>>> Hi,
>>> On Sun, Mar 6, 2011 at 12:04 PM, Anton Khirnov<anton at khirnov.net> ?wrote:
>>>> AVIOContext.is_streamed field should be used directly instead.
>>> Since we're talking about API cleanup anyway. What is this function?
>>> A "stream" isn't a very useful concept. Why do demuxers want to know
>>> whether the input is a stream? They more likely want to know whether
>>> the input is seekable (like HTTP/1.1 with RangeRequest vs. HTTP/1.0 or
>>> a pipe/fifo), or whether seeking - if supported at all - is slow (like
>>> HTTP/1.1 with RangeRequest vs. a local seekable file). I see it used
>>> in a variety of different demuxers with a different implied meaning
>>> (seeking is slow vs. seeking is unsupported), and that is bad.
>> change it to:
>> seekable=0 //no seeking
>> seekable=1 //slow seeking
>> seekable=2 //fast seeking
>> enum could be used
> You could possibly add "can't SEEK_END" to that list. One example of that
> would be a growing HTTP resource (like pointing to a file being uploaded),
> where you can seek anywhere but past the current end of the stream/file.

That's why I like a flags field for this, because it allows us to add
more later on.


More information about the ffmpeg-devel mailing list