Claudio Ciccani wrote: > [EMAIL PROTECTED] wrote: >> New commits: >> http://git.directfb.org/?p=extras/DirectFB-extra.git;a=commit;h=743cfefb9d56d32b203ec9a5f6b3ac3e7f39d039 >> commit 743cfefb9d56d32b203ec9a5f6b3ac3e7f39d039 >> Author: Denis Oliver Kropp <[EMAIL PROTECTED]> >> Date: Fri Nov 2 15:23:05 2007 +0100 >> >> Implemented Attach/DetachEventBuffer() in Xine video provider, sending >> different events. >> >> Also added locking and cleaned up code slightly. >> > > Why locking? > xine is already thread-safe (i.e. each function in xine-lib already > handles itw own lock).
Hmm, I looked at some functions and did not see locks in there. Anyhow a few places should use locking to protect the data of the provider itself. At least the event buffer registration, sending events and start/stop of playback. I can remove some of the locking or even revert it. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
