Brad Garton

Related to the settings of weirdly-named things like "slop" and

"overdrive", I wouldn't mind a tech area in the SDK with a clear

layout of msp threading, priority, queue service, etc. I still

don't quite get the real effect of putting elements at the head or

tail of the various defer-(low/medium/---)queues, and how best to

employ the defer mechansim for various operations. Sorry I'm so

dense about this... I really don't see how the threading priorities

Related to the settings of weirdly-named things like "slop" and
"overdrive", I wouldn't mind a tech area in the SDK with a clear
layout of msp threading, priority, queue service, etc.  I still
don't quite get the real effect of putting elements at the head or
tail of the various defer-(low/medium/---)queues, and how best to
employ the defer mechansim for various operations.  Sorry I'm so
dense about this... I really don't see how the threading priorities
are established.

no-subject-9

On Mar 7, 2007, at 7:44 AM, garton@columbia.edu wrote:

> Related to the settings of weirdly-named things like "slop" and

> "overdrive", I wouldn't mind a tech area in the SDK with a clear

> layout of msp threading, priority, queue service, etc... I really 

I would suggest checking out my "Event Priority in Max (Scheduler vs. 

Queue)" article and then get back to us with specific questions:

https://cycling74.com/story/2005/5/2/133649/9742

> Related to the settings of weirdly-named things like "slop" and
> "overdrive", I wouldn't mind a tech area in the SDK with a clear
> layout of msp threading, priority, queue service, etc... I really  
> don't see how the threading priorities
> are established.

I would suggest checking out my "Event Priority in Max (Scheduler vs.  
Queue)" article and then get back to us with specific questions:

(no subject)