Hello, On Tue, Dec 17, 2013 at 9:54 PM, dumblob <[email protected]> wrote: >> In the end, what raster said is true, out of all the EFL C API, only some is >> thread safe. The EFL design does include mechanisms for marshalling unsafe >> calls to the main thread. So it doesn't matter which scripting language is >> used to wrap it, somewhere along the line this call marshalling will have to >> be taken care of. > > Nice, this is what I wanted to know. Now it's apparent it's (and will > be) possible to use pure pthreads from C without EFL thread-wrappers > under the condition the programmer passes explicitly serialized > messages (using thread-safe serializing C functions) to those > thread-unsafe C functions.
I would still recommend you to use at minima Eina_Thread infrastructure so you get portability out of the box. Also Ecore_Thread provide all the infrastructure needed to synchronize with the main loop with the minimum possible cost (limit the number of wake up in the main loop and the amount of data marshaled to fd to the bare minimum). Current limitation that I do think is annoying is the lack of mechanism to transmit data between thread. That would be an improvement for future, that would make those thread close to some mini main loop. -- Cedric BAIL ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
