-=> Quoting Harry Wesebaum to Jack Stein <=-
 HW> *My* understanding of Session_Priority is the exact opposite. The
 HW> higher number gets priority first and the lower numbers are last on
 HW> the service list.
 HW> Which of us is right?
        Both.
        In Winders95, the Session_Pri option (as defined in the SDK and 
PI's)
define that the HIGHER the priority, the more that thread can be delayed 
ntil
there is a wait period, or threads are polled.
        In OS/2, it's exactly the opposite (which, in my opinion, makes more
sense): A Session_Priority of 32 is the HIGHEST priority, and priorities of 1
are the lowest priority. On my OS/2 Connect system, EVERYTHING is set to 1.
This makes for very smooth multitasking.
        Winders has always taken off on their own tangent, and tried to
redefine their back-asswards ideas as "The Standard". Looking at the API just
reinforces this fact.
-The Visionary
visionary@brazerko.com
... "Captain, why not just give the Borg Windows 3.1?" - Worf
--- WtrGate+ 0.93.PRE2 ALPHA sn 116
---------------