We've received numerous requests for multiple event queues in the AWT,
and if we're to do it in 1.2, now is the time.  We don't dare do such
a significant change a few months from now.

To implement multiple event queues, we really need to re-enable multiple
AppContexts, which was disabled by Tom on February 25th until the key
could be computed reliably.

The key for AppContexts was the security context.  My current
understanding of the problem was that if we were in priveleged code, the
security context was that of the priveleged code, so the AppContext was
computed incorrectly.

It seems to me that the needs of an AppContext key are different from
that of security.  When computing the AppContext, we are concerned with
the instance of the earliest AppContext-controlling object on the call
stack.  Entering priveleged code shouldn't affect this at all.

I anticipate that we'll need a method in the VM similar to
JVM_GetStackAccessControlContext() to do this for us, which we'll use
to find the current AppContext.

This is a significant departure from the earlier AppContext key based
on security context, but I think this makes sense.  My other
concern is performance.  It's hard to compete with stubbed code for
performance.  :-)