[Live-devel] make the live555 scheduler working together with other schedulers

Alberto Alberici albalber at yahoo.com
Fri Mar 26 06:14:46 PDT 2010


I specified that I don't want to use threads...

Is there another way to solve?


--- On Mon, 3/22/10, Matt Schuckmannn <matt at schuckmannacres.com> wrote:

From: Matt Schuckmannn <matt at schuckmannacres.com>
Subject: Re: [Live-devel] make the live555 scheduler working together with other schedulers
To: "LIVE555 Streaming Media - development & use" <live-devel at ns.live555.com>
Date: Monday, March 22, 2010, 11:13 PM





  
My approach for this kind of stuff has been to put them in separate
threads (I'd probably create a thread for Live555) and then just use
some sort of thread safe communication for passing events and data
between the 2, e.g. a socket or thread safe queue, etc. 



Matt S. 





On 3/22/2010 2:27 AM, Alberto Alberici wrote:

  
    
      
        Hi,

        

which is the best way to make the live555 library work together with
another library which has its own main scheduler (for example: qt),
_without using threads_?

        

I mean: qt has app.exec(), which doesn't return, and live555 has
doEventLoop(), which doesn't return.... Of course I could write
MyScheduler and then call singleStep(), which returns, instead of
calling doEventLoop(), but in this case singleStep() would return only
after the select() wait (and this would block the other library,
meanwhile) ....

        

thanks

        
      
    
  
  

  
_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
  

 

-----Inline Attachment Follows-----

_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20100326/6902d949/attachment.html>


More information about the live-devel mailing list