Dear Sir:

After reviewing the server side implementation, I think the streaming
process is a pull model, isn't it?

Besides, when the frame data is pulled readily, the event loop will
scheduled to send the frame immediately no matter the output channel is over
UDP or TCP, won't it?

The problem is that if two clients, one of which is over UDP while the other
is over TCP and has only limited bandwidth, the transmitting rate of the UDP
client seems to be influenced by the slow TCP client, right?

If such a problem does exist, how about separating the tcp sending process
from the frame pulling one and doing the sending in the event loop only when
the output tcp socket is writable?

Of course, one should handle the coded frame dropping issue if the prepared
tcp sending buffer is full.

Is my reasoning OK?

BR
Fuzzy Lai
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to