[FFmpeg-devel] Network IO in FFmpeg (was: abstractable threading api)
Michael Niedermayer
michaelni at gmx.at
Mon Dec 23 15:33:27 CET 2013
On Mon, Dec 23, 2013 at 01:04:01AM +0100, Nicolas George wrote:
> Le nonidi 29 frimaire, an CCXXII, Nicolas George a écrit :
[...]
> Input-driven processing
>
> If we have a thread, then we are notified as soon as data arrive on the
> socket. We could add an API to register a callback to forward the
> notification to the application immediately; the callback would have to be
> fast, of course.
>
> This would be especially beneficial for protocols that use several
> underlying sockets: they all implement their own poll()-based stuff. It is
> an actual miracle that they work more or less reliably with that poll() and
> the UDP thread at the same time.
at least for build_udp_url() in rtpproto.c we disable the udp thread
because it does not work together
>
> Input-driven processing with a callback would simplify greatly all that, and
> probably make it more efficient too.
>
> (There is the small issue of getting it to work without threads too, but I
> believe it can be managed.)
>
> Regards,
>
> --
> Nicolas George
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
You can kill me, but you cannot change the truth.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20131223/16ccc867/attachment.asc>
More information about the ffmpeg-devel
mailing list