[FFmpeg-devel] [PATCH 1/3] Non-blocking protocols: flag and documentation
Ronald S. Bultje
Sat Feb 5 21:35:22 CET 2011
On Sat, Feb 5, 2011 at 2:04 PM, Luca Barbato <lu_zero at gentoo.org> wrote:
> On 02/04/2011 08:01 PM, Ronald S. Bultje wrote:
>> On Fri, Feb 4, 2011 at 1:12 PM, Nicolas George
>> <nicolas.george at normalesup.org> wrote:
>>> Signed-off-by: Nicolas George <nicolas.george at normalesup.org>
>>> ?doc/APIchanges ? ? | ? ?3 +++
>>> ?libavformat/avio.h | ? 29 ++++++++++++++++++++++++++---
>>> ?2 files changed, 29 insertions(+), 3 deletions(-)
>>> ?Changes since the last time I sent these patches:
>>> ?- First one (factor poll in TCP) got applied; rest rebased on the current
>>> ? head.
>>> ?- Doxygen group for URL_RDONLY/URL_RDWR/URL_WRONLY.
>> I'm basically willing to apply this, I'm wondering if we need a flag
>> to indicate which URLProtocols support non-blocking opening. Anyone
>> have opinions on this? Or should we just assume it'll always be
>> supported for all protocols? (Does file/pipe/etc. support it now?)
> I'm ok with the patch, I'm not sure which protocol should not support
> non-blocking but if we implement some kind of hardware specific protocol
> it might have some specificities.
So "let's deal with it if a problem arises"? Is fine with me, I'll
leave this for one day for others to comment on and merge tomorrow
(please ping me if I forget).
More information about the ffmpeg-devel