>> General Users = safety, if any of these loaders crash or hung, the main >> program/process will not crash. > > actually... hanging can be a problem as evas opens a pipe and waits on blocking > input. it has no timeout, so if it hangs, evas using process will too. you can > just kill the external loader process pid and the app will unhang (and then > load fails) - so its recoverable, and probably a sign to uninstall that > specific external loader and file a bug. :)
wait....what?? no timeout for an external pipe?? isn't that a design flaw? you're just saying it, if the external process hungs, evas hungs. Who do you think users will blame? I know, you're probably going to say that an external loader could take a lot of time (i'm imaging a 70MB pdf with lots of pictures and stuff). But that's not a reason to not have a timeout, at least set a long timeout, like 60 or 90 secs. And after that time, also try to kill the piped PID (though I'm not sure if it's possible to do that) Or I'm saying stupid things again and I have to go back to my cave? 2011/5/13 Carsten Haitzler <ras...@rasterman.com> > On Fri, 13 May 2011 15:47:20 -0300 Gustavo Sverzut Barbieri > <barbi...@profusion.mobi> said: > > > On Fri, May 13, 2011 at 2:50 PM, Wido <wido...@gmail.com> wrote: > > > > > Excelent!!! but what is the first impact for non-developers users? > > > > > > > End Users = more image formats supported, like gimp (xcf) and pdf. > > > > Proprietary Users = you can use Evas (declared BSD, really LGPL due Eina) > in > > your proprietary application and use GPL library loaders as they're out > of > > process, thus no license linkage problems. > > well not really. evas doesn't become lgpl because it links to an lgpl lib > :) > but the point is still right - apps are unaffected by license of external > generic loaders, so we can expand the # of formats evas can load in the > "gpl" > direction AND in the "it's complex and/or unstable" direction (html, > ppt/doc/xls etc. loaders and so on). it basically makes it all possible > (but as > you noted - there is a cost). > > > General Users = safety, if any of these loaders crash or hung, the main > > program/process will not crash. > > actually... hanging can be a problem as evas opens a pipe and waits on > blocking > input. it has no timeout, so if it hangs, evas using process will too. you > can > just kill the external loader process pid and the app will unhang (and then > load fails) - so its recoverable, and probably a sign to uninstall that > specific external loader and file a bug. :) > > > Problems: this is not as fast as a native loader, so we'll not move every > > (if any!) loader to be external. > > yeah. that's its major Achilles heel. it has a speed and overhead penalty. > > > > > -- > > Gustavo Sverzut Barbieri > > http://profusion.mobi embedded systems > > -------------------------------------- > > MSN: barbi...@gmail.com > > Skype: gsbarbieri > > Mobile: +55 (19) 9225-2202 > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > -- Wido ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
