(First, please do not post the same question to the list multiple times.)
Yes, this is an issue, and is a good illustration why it's ill-advised to
structure a LIVE555-based application using multiple threads.
However, in some future release, I'll make the "OutPacketBuffer::maxSize"
variable a
Hi Ross,
It seems that we meet, times to times, a problem related to the static variable
OutPacketBuffer::maxsize between multiple live555 environment running in
different threads.
Basically it seems that creating a RTCPClient change the static
OutPacketBuffer::maxsize, but if
Hi Ross,
It seems that we meet, times to times, a problem related to the static variable
OutPacketBuffer::maxsize between multiple live555 environment running in
different threads.
Basically it seems that creating a RTCPClient change the static
OutPacketBuffer::maxsize, but if a
Hello Ross,
sorry for the late reply.
I'm afraid replacing the 2 "for" loops with the code you provided
generates a segmentation fault in our app.
Of course, it may be something in our application so I'll run more tests
today and will provide you with more information as soon as I can.
Than
Hi Everyone
i made a live media server client through sliverlight (TCP socket and
network stream),i am able to read the first chunk(response of GET request)
which contain info like:-
HTTP/1.1 200 OK\r\nDate: Thu, May 03 2012 07:47:59 GMT\r\nServer: LIVE555
Streaming Media v2011.11.29\r\nLast-Modif
