[FFmpeg-devel] [PATCH] RTSP-MS 14/15: ASF packet parsing
Ronald S. Bultje
Wed Apr 22 02:29:53 CEST 2009
On Tue, Apr 21, 2009 at 1:33 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
> There seem 2 variants and i belive both should be implemented because
> they are both usefull in different circumstances.
> The first is that the rtp code should provide a fully functional
> ByteIOContext, not one that has a EOF before the end of the file.
> That means it must provide a read_packet() callback.
> Such callback would of course block until the data has been received.
> This first variant is usefull for a multithreaded application that runs
> the demuxer in a seperate thread and is thus unaffected by the blocking.
> The second is that when no more data is available this
> state should be signaled to the demuxer (iam not sure if we have any
> means to do this yet) also iam not sure which way is the nicest to
> do this
> a url_fwouldblock() could be used, that is the asf demuxer could do
> ? ?return AVERROR(EAGAIN);
> before reading the first byte of the next packet
> Either way comments and alternative suggestions are definitly welcome.
Any ideas about a push-based instead of pull-based mechanism / basis
for the demuxer?
</let's throw in some crazy idea and wait for a flamewar>
More information about the ffmpeg-devel