Hi, On Wed, Apr 6, 2011 at 5:20 PM, Anton Khirnov <[email protected]> wrote: > On Wed, Apr 06, 2011 at 05:16:37PM -0400, Ronald S. Bultje wrote: >> On Mon, Apr 4, 2011 at 2:43 PM, Anton Khirnov <[email protected]> wrote: >> > +/** >> > + * Use non-blocking mode. >> > + * If this flag is set, operations on the context will return >> > + * AVERROR(EAGAIN) if they can not be performed immediately. >> > + * If this flag is not set, operations on the context will never return >> > + * AVERROR(EAGAIN). >> > + * Note that this flag does not affect the opening/connecting of the >> > + * context. Connecting a protocol will always block if necessary (e.g. on >> > + * network protocols) but never hang (e.g. on busy devices). >> > + * Warning: non-blocking protocols is work-in-progress; this flag may be >> > + * silently ignored. >> > + */ >> > +#define AVIO_FLAG_NONBLOCK 4 >> >> I believe this is only implemented at the URLContext level, not at the >> AVIOContext level. It's one of those things that makes you wonder why, >> but anyway. >> >> Should this be exposed as part of the public API? >> >> (I know the comment says it's ignored, but that's just lame. Nobody is >> working on this. This will stay here for 10 years and then we'll >> remove it in a next major cleanup.) > > The flags from avio_open are passed to ffurl_open, so setting this flag > will have an effect. And AFAIK it is implemented in TCP and UDP > protocols.
Can anyone confirm this? I wasn't aware that it'd work across URLContext -> AVIOContext. If so, patch is fine. Ronald _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
