On Fri, Apr 2, 2010 at 1:10 AM, Ross Finlayson wrote:
> I personally find your disdain for threads antiquated and naive
>>
>
> This shows a lack of understanding. It's like saying that the designers of
> a bullet train have a "disdain" for air transportation, or conversely that
> the designers of
I personally find your disdain for threads antiquated and naive
This shows a lack of understanding. It's like saying that the
designers of a bullet train have a "disdain" for air transportation,
or conversely that the designers of an aircraft have a "disdain" for
rail transport. On the cont
I interpret what the OP is doing as this section in the FAQ:
"Another possible way to access the code from multiple threads is to
have each thread use its own "UsageEnvironment" and "TaskScheduler"
objects, and thus its own event loop. The objects created by each
thread (i.e., using its own "U
This is what I'm doing and haven't had a problem yet with our test
servers. What I'm more interested in is from the original post:
Does LiveMedia library conform to RTSP standard in this matter or
maybe it is a bug in Sanyo devices ?
I would think that even in single-threaded usage, if multip
On 4/1/2010 7:06 PM, Ross Finlayson wrote:
I've found out that when you run a few different instances of RTSP
clients in separate threads CSeq number is not increased by one with
each consecutive request.
It's because CSeq number is a static variable in RTSPClient.
This is a perfect illustrat
On Thu, Apr 1, 2010 at 7:06 PM, Ross Finlayson wrote:
> I've found out that when you run a few different instances of RTSP clients
>> in separate threads CSeq number is not increased by one with each
>> consecutive request.
>> It's because CSeq number is a static variable in RTSPClient.
>>
>
> Thi
>
> I've found out that when you run a few different instances of RTSP clients
>> in separate threads CSeq number is not increased by one with each
>> consecutive request.
>> It's because CSeq number is a static variable in RTSPClient.
>>
>
> This is a perfect illustration of why you are not suppos
I've found out that when you run a few different instances of RTSP
clients in separate threads CSeq number is not increased by one with
each consecutive request.
It's because CSeq number is a static variable in RTSPClient.
This is a perfect illustration of why you are not supposed to run
LIVE
Hi,
I've found out that when you run a few different instances of RTSP clients
in separate threads CSeq number is not increased by one with each
consecutive request.
It's because CSeq number is a static variable in RTSPClient. It has an
unexpected side effect - SANYO network cameras end RTSP sessio
