On Wed, 8 Jun 2016 22:37:55 +1000 David Seikel <onef...@gmail.com> said:

> I'm just gonna pipe in here a little bit.
> 
> On Wed, 8 Jun 2016 20:16:20 +0900 Carsten Haitzler (The Rasterman)
> <ras...@rasterman.com> wrote:
> 
> > > If history tell us, our existing solution is not usable, but prove
> > > me wrong and show me how amazing our current limited set of
> > > asynchronous API is used by so many people. Now just think that we
> > > are expanding  
> > 
> > as above. ecore_con. ecore_con_url, preload, timer, job,
> > animator, .... all used.
> 
> I use ecore_con, timer, job, and animator in a couple of my projects.
> The first two I use a lot in my huge project.  ecore_con_url and
> preload I just haven't bothered to try out yet.  I also use EFL
> threads and ecore fd handler for some async stuff.
> 
> There was one thing I was thinking that I might try promises on, once
> the API and arguments are settled, replacing timer and job for
> sequencing some async startup stuff.  That would still leave ecore_con,
> timer, and threads heavily used in that project, but I think that's the
> only place I use job.  Promises as initially described to me seems like
> a slightly better fit than timers and jobs for this startup stuff.
> 
> I've not actually looked at promises yet though, but I agree in
> principle with Raster when he says that things should be consistent and
> use the same infrastructure.  Having said that, now I'm wondering why we
> can't just extend jobs?

actually jobs in current efl are promises, so it's kind of inverted. but
promises are objects. a job is now a promise. you want to track it and
cancel/unref/whatever it hwne you no longer need it. this is why i keep saying
they are objects thus should be eo.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to