On Wed, 9 Apr 2008 15:55:57 +0200 "Cedric BAIL" <[EMAIL PROTECTED]> babbled:
> I arleady though about some other possibilities : > - make it optional in configure > - only start it when required, but that's much more complex > - only initialise it from required sub system (like later the cache > subsystem), but this will render useless the call to > evas_async_events_process in some case. i think that non-blocking for reads are something we need. calling the process call needs to do nothing if there is nothing to read (and just return). it should be optional - sure, so things that would be done async are done inline without a thread if disabled (things just block instead). -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
