[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ccrtp-devel] SchedulingTimeout problem
From: |
Federico Montesino Pouzols |
Subject: |
Re: [Ccrtp-devel] SchedulingTimeout problem |
Date: |
Tue, 21 Sep 2004 14:49:03 +0200 |
User-agent: |
Mutt/1.5.6+20040818i |
Looks interesting, however, the new run method waits for WAIT_DATA_TIMEOUT.
would it block the reception service when there are no outgoing packets?
After a first look I got that impression.
On Tue, Sep 14, 2004 at 01:55:16PM +0200, Guillaume Glodas wrote:
> Hi,
>
> When there is no data to send, the ccrtp thread waits until
> defaultSchedulingTimeout is reached even if data are pushed in the
> queue. When defaultSchedulingTimeout is too high it can cause packet to
> be sent too late, when defaultSchedulingTimeout is too small it can
> increase the load of the computer.
> That's why we propose to replace this timeout with a
> OutgoingDataQueue::waitData method which waits until the queue is no
> more empty or a timeout is reached. It seems to dicrease computer load.
> What do you think about this modification?
> Regards,
>
> Guillaume Glodas
>