Re: How To Get Idle Time to the edit and view components?
Re: How To Get Idle Time to the edit and view components?
- Subject: Re: How To Get Idle Time to the edit and view components?
- From: Philippe Wicker <email@hidden>
- Date: Wed, 4 Jun 2003 14:54:03 +0200
On Wednesday, June 4, 2003, at 01:45 PM, Urs Heckmann wrote:
Am Mittwoch, 04.06.03, um 11:30 Uhr (Europe/Berlin) schrieb Shai
Shasag:
Eric has recently asked: How To Give Idle Time From The AU To The
Host ?
I would like to add the question of how to get idle time for the view
and edit component?
Hi all,
This post is a little bit OT. Excuse my ignorance, but the "concept" of
giving or getting idle time has always looked obscure to me so I seize
the occasion to ask knowing people some enlightenment on this topic. My
understanding is that "idle time" is requested when some work has to be
done "on the background" when the CPU is "free". Is that right? It
looks like a cooperative cpu resource dispatching. Because this
"dispatching" is realized by an event loop (probably the main UI loop),
slices of idle time may be used to accomplish some work in the event
loop thread context. This mechanism appears to me like a survival of
non multithreaded and/or non preemptive OS epoch. I mean that if you
don't need to do the job in the event loop thread context, a low
priority time shared thread could do the same. On the other hand, if
you do need to do the job in the event loop thread (eg to avoid
concurrent accesses to shared data), then this "idle time" dispatching
appears to be a good solution. Again, I'm quite ignorant on this topic
so I may be totally wrong.
Thanks for any answer. Maybe an illustration of "idle time" use case?
Philippe Wicker
email@hidden
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.