The LiveMedia library uses the magical world of select(), which
allows for monitoring multiple file handle descriptors (or in this
case, sockets) to monitor for incoming/outgoing data.
More precisely: The "LIVE555 Streaming Media" libraries use the (not
so magical) world of events, whereby eve
Hi.
Thanks for the explanation.
2009/8/25 Jerry Johns
> The LiveMedia library uses the magical world of select(), which allows
> for monitoring multiple file handle descriptors (or in this case, sockets)
> to monitor for incoming/outgoing data.
>
> By blocking on this select() call, an event l
ve555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Stas Oskin
Sent: Monday, August 24, 2009 3:14 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] multiple instances of live555 library
Hi Ross.
You don't do this. Please every
Hi Ross.
You don't do this. Please everybody, read the FAQ!
>
> The "LIVE555 Streaming Media" software uses an event loop (a single thread
> of control) for concurrency, instead of using multiple threads.
>
Sorry for barging into this thread - an architecture question if I may. I
expirirmented w
Ross,
I found my problem was caused by other element in my system.
But after I gave it more thought, I think the situation I had actually was
not using multiple instances of live555.
The module I developed is a shared library which is loaded by a host
program which I have no control. Each mo
Is there anything I have to be aware to use multiple instances of
live555 library in a single process?
You don't do this. Please everybody, read the FAQ!
The "LIVE555 Streaming Media" software uses an event loop (a single
thread of control) for concurrency, instead of using multiple threads.
Hi,
I'm developing an H264 RTP source filter for the Microsoft Directshow
platform. The directshow filter is basically a shared library which is
loaded dynamically. I created BasicTaskScheduler, BasicUsageEnvironment and
MediaSession when the filter is loaded. If there is only one instance of
