[FFmpeg-devel] [PATCH] Non-blocking protocols (original) (raw)
Luca Barbato lu_zero
Mon Jan 31 16:53:28 CET 2011
- Previous message: [FFmpeg-devel] [PATCH] Non-blocking protocols
- Next message: [FFmpeg-devel] [PATCH 1/3] Non-blocking protocols: flag and documentation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 01/31/2011 04:32 PM, Ronald S. Bultje wrote:
General comments: - if we have a non-blocking API, then we should have a library function to get FDs and/or poll them. Is that available through url*() API? I believe it is, because rtsp.c uses it, but just want to make sure
We might consider something slightly more structured and or consider implementing network double buffering (to solve the issue we are having with the kernel network buffers being too small to keep all the data between calls)
- this is just for protocols, not demuxers, right? Should we introduce a flag to indicate which protocols support non-blocking red/write? This'd be nice for things like webcams and so on also at some point
our avdevice has a similar problem for the output (the loop is driven by the decoding process while some apis expect to be able to be the driver...)
lu
--
Luca Barbato Gentoo/linux http://dev.gentoo.org/~lu_zero
- Previous message: [FFmpeg-devel] [PATCH] Non-blocking protocols
- Next message: [FFmpeg-devel] [PATCH 1/3] Non-blocking protocols: flag and documentation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]