On Wed, Apr 13, 2016 at 3:47 AM, Carsten Haitzler <[email protected]> wrote: > i'm wondering... shouldn't we make eo and eo base "threadsafe". ie a basic eo > object should have locks around things like:
I am not to sure of the intended idea of making eo threadsafe for all of those function. If you are using the same object from two differents thread, it is pretty certain in my opinion that you will need to have lock to manage its use yourself or you will end up with crash. I don't think it is possible to build a threadsafe and safe to use API that won't require the user of that API to actually think about where to put lock. So if we advertise our API as threadsafe and the developer don't understand the limit of it (Like most Java developers for example), he will manage to have race condition and blame Eo for not being properly threadsafe. I believe it will result in a more complex use of eo, when can I rely on it being threadsafe, when can't I ? Which is why I don't think this is a good idea. -- Cedric BAIL ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
