Hello, On Tue, 2007-05-08 at 16:59 +0200, Alexander Larsson wrote: > I'm still not sure why gstreamer needs to run its own mainloop in its > thread though. If its async, then it should be able to use the default > mainloop. Is it because there is no guarantee of the default mainloop > running always?
I am not certain how the mainloop got involved here. GStreamer uses threads so that it can use blocking read() and write() calls. Underneath, it's true they go through select() first on the fd + a control fd from a socketpair, because you need to be able to cancel a wait from another thread, so that you can seek, for example. Perhaps that is the concern? In any case, as long as one is able to cancel an in-progress sync operation from another thread, GStreamer is fine, AFAIK. Regards, Andy. -- http://wingolog.org/ _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
