On Thu, Jul 21, 2011 at 1:06 AM, Ross Finlayson wrote:
> Now, I don't see how. (I assume you're not doing something dump like
> trying to use more than one thread.)
I'm using a dedicated thread for each Live555 instance.
Could it have to do with the session having multiple subsessions? The
se
Is it somehow possible that something else could read from the
socket between when AWAITING_STREAM_CHANNEL_ID is set and the case
statement?
Now, I don't see how. (I assume you're not doing something dump like
trying to use more than one thread.)
And would it be possible to complete the
On Wed, Jul 20, 2011 at 4:41 PM, Ross Finlayson wrote:
> **
>
> Any ideas why this may be happening?
>
>
> Unfortunately not.
>
Is it somehow possible that something else could read from the socket
between when AWAITING_STREAM_CHANNEL_ID is set and the case statement? And
would it be possible to
Any ideas why this may be happening?
Unfortunately not.
So I did a quick test with the following code:
case AWAITING_STREAM_CHANNEL_ID: {
// The byte that we read is the stream channel id.
RTPInterface* rtpInterface = lookupRTPInterface(c);
if (rtpInterface != NULL)
On Wed, Jul 20, 2011 at 11:15 AM, Jeremy Noring wrote:
> I updated my RTP client to the most recent version (2011.7.18) and I'm
> having trouble with RTP over TCP. Occasionally Live555 will get in a state
> where it no longer receives any data from the server, even though the server
> is complet
