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

[Silvain Beriault]

Hello,

According to the DeviceSource.cpp template, the doGetNextFrame() should 
deliver a frame "in a non-blocking fashion i.e., so that we return 
immediately from this function even if no data is currently available."

However, if no data is available, the afterGetting() function is not 
invoked within doGetNextFrame (since no new data is delivered) and this 
causes the doGetNextFrame() function never to be called again by the 
internal live555 API.  Any suggestions on how this problem should be 
handled?

Thank you!
Silvain