Hi Ross,
Thanks for your response.
>I'm not interested in any alleged server bug, unless the server is
>running an up-to-date version of our software (in which case it
>doesn't matter what version of our software the client is running, or
>whether or not the client is using the synchronous or asy
Could you please clarify this a bit? If I understand correctly, we
must therefore upgrade
both our server and client code to use the latest live media version
to avoid the server
hanging? Or would updating the client code to use the new async
RTSPClient code suffice?
I'm not interested in any al
In case it helps: profiling shows that the following seems to account
for the CPU usage:
void SocketDescriptor::tcpReadHandler(SocketDescriptor*
socketDescriptor, int mask) {
socketDescriptor->tcpReadHandler1(mask);
}
Commenting out the dummy descriptor on fReadSet didn't help solve the issue.
Hi Ross,
We use the LIVE555 Streaming Media library to implement a live streaming server
(on Ubuntu) and a windows media player RTSP client streaming RTP over
TCP only.
We have run into a complicated set of problems recently:
1) When a client with a *bad* internet connection joins the RTSP
server
