Re: [Ccrtp-devel] How to block on incoming queue?

[David Sugar]

The common reason for not getting data right at arrival is that rtp udp
packets can arrive out of order.  The receive queue is used to assure
packets can be returned properly ordered to the application, as well as
to account for late arrival and jitter.

Yaniv Levy wrote:
> Thank you for your swift answer.
> 
> I'm not looking to block on the socket. This is internal to the RTPSession
> class and wisely hidden from the application.
> I'm looking to block on the incoming queue, since my application draws data
> from the queue and not from the socket.
> 
> Indeed, The only way I thought about to accomplish it was like you were
> saying: redefine RTPSession::run() method. it will do exactly what it does
> in RTPSession, and signal my application using a function call or condition
> variable.
> 
> I find it interesting that this issue was not asked previously. i want to
> get the packet as fast as it gets into the incoming queue. maybe most
> application don't.
> 
> Thank you very much.
> Yaniv
> 
> On 5/23/06, Federico Montesino Pouzols <address@hidden> wrote:
>>
>>
>> Hi, I guess isPendingData and isPendingControl are the methods you are
>> looking for. These methods block waiting for available packets on the
>> data/control reception socket (you can specify a max. timeout). If you
>> want to somehow modify the service thread behavior, you can inherit
>> from RTPSession and redefine the run method in rtp.h.
>>
>> Also, if there are no packet in the incoming queue, getFirstTimestamp
>> will return 0.
>>
>> HTH.
>>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ccrtp-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/ccrtp-devel

dyfet.vcf
Description: Vcard