[Live-devel] Blocking vs Non-Blocking doGetNextFrame()???

[Ross Finlayson]

>Thank you for your suggestions. In my application, data is being 
>pulled from a circular queue containing uncompressed video data 
>which I compress and write to fTo within the doGetNextFrame() 
>function. My application is multi-threaded (with a single thread 
>accessing the live555 API as mentioned in the FAQ). So under those 
>premise, do you see any potential problem with having a 
>doGetNextFrame() function that blocks when there is no data 
>available in the queue?

Yes.  If you block, waiting for new data, then no other events will 
be handled (by the event loop) in the meantime.  That is why 
"doGetNextFrame()" should not block.
-- 

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/