> The master doesn't only have the fusion read thread, but input threads, > too.
Of couse i was only saying that this way it is possible to remove the messaging thread of the master :-) > I have some concerns regarding the patch. The main problem is that not all > messages are related to IDirectFBEventBuffer. So there has to be a more > central mechanism. I'm not sure if it's fully safe at all not to listen all > the time. > > Is anyone familiar with async io? Any other ideas? Hi Mh, ... i guess that you are thinking about things like reactions, with which for instance "IDirectFBSurface" can get aware that the CoreSurface has been destroyed/resized, but maybe this things should be checked sincronously at every call, since doing it asyncronously with a thread could be even less safe than waiting for a check of /dev/fusion... Or maybe unix signals could be used, the fusion module could send a SIG_SOMETHING to the app when new messages are avalable, and a handler could read /dev/fusion? Are unix signals and threads the only way you can do async aswers? Hi Maurizio -- Your mouse has moved. Windows must be restarted for the change to take effect. Reboot now? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
