One of the things I have come to expect from using
handlers is that they run at a priority above the
main thread. In particular, if the main thread and
a handler competes for a processing resource the
handlers wins.
Maybe I am misunderstanding the specification, but isn't
it possible that a handler which becomes runnable (a
message has been received) may not execute immediately
because the main thread which might also be runnable has
control over the processing resource (when there is only
one resource). I don't see anything in the specification
that would negate this possibility. I can understand
handlers being blocked by other handlers but not by
non-handler threads.
Perry Partow
NCCOSC, RDT&E Div.